[issue44869] MacOS Monterrey malloc issue

Ned Deily added the comment: The crash report you provide shows a crash in libstdc++ which is normally not called directly by the Python interpreter or standard library modules on macOS but appears to be being called by libopenblas as provided by the copy of numpy in use. Suggest you follow

[issue44869] MacOS Monterrey malloc issue

Change by Eduardo Morales : -- versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue44869] MacOS Monterrey malloc issue

Eduardo Morales added the comment: Also: (base) ➜ backend git:(development) ✗ PYTHONFAULTHANDLER=1 python3 server.py CONFIG_FILE=../config/development.json Python(27657,0x10839f600) malloc: *** error for object 0x7ffb4ac81d10: pointer being freed was not allocated Python(27657,0x10839f600) m

[issue44869] MacOS Monterrey malloc issue

Eduardo Morales added the comment: Not sure if this is helpful, but I am attaching the MacOS bug log that is auto-generated when Python fails. -- Added file: https://bugs.python.org/file50267/bug.log ___ Python tracker

[issue44869] MacOS Monterrey malloc issue

Ronald Oussoren added the comment: There is a 3th possibility: This could be a bug in the OS, Monterey is still in beta at this point and beta's tend to contain more bugs than release versions. -- ___ Python tracker

[issue44869] MacOS Monterrey malloc issue

Eduardo Morales added the comment: I've been able to tackle the issue down and reported it to the library. Although I'm not sure if it's a Python or library issue. https://github.com/ibmdb/python-ibmdb/issues/648 -- ___ Python tracker

[issue44869] MacOS Monterrey malloc issue

Ronald Oussoren added the comment: I'm afraid we cannot do a lot with the information you provided. I've just ran a full test run for a copy of 3.10rc1 installed using the universal2 installer and that doesn't have problem. One way to find more information about what's going on is to use fau

[issue44869] MacOS Monterrey malloc issue

Change by meowmeowcat : -- components: +macOS nosy: +ned.deily, ronaldoussoren type: -> crash ___ Python tracker ___ ___ Python-bug

[issue44869] MacOS Monterrey malloc issue

Eduardo Morales added the comment: These are the libraries that I'm using: ``` ibm-db~=3.0.4 Flask~=2.0.1 pandas~=1.2.5 requests~=2.25.1 flask_basicauth~=0.2.0 schedule~=1.1.0 ``` -- ___ Python tracker _

[issue44869] MacOS Monterrey malloc issue

Eduardo Morales added the comment: I am not sure how to reproduce it, I think it's being caused by an imported library. -- ___ Python tracker ___

[issue44869] MacOS Monterrey malloc issue

New submission from Eduardo Morales : Running on MacOS Monterrey throws following error: ```malloc: *** error for object 0x7ffb5ea1a120: pointer being freed was not allocatedPython(4899,0x1061a8600)``` This started happening right after upgrading to the new MacOS Beta. -- messages: 3