[issue44869] MacOS Monterrey malloc issue

2021-09-07 Thread Eduardo Morales
Change by Eduardo Morales : -- versions: +Python 3.11 ___ Python tracker <https://bugs.python.org/issue44869> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44869] MacOS Monterrey malloc issue

2021-09-07 Thread Eduardo Morales
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

[issue44869] MacOS Monterrey malloc issue

2021-09-07 Thread Eduardo Morales
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 <https://bugs.python.

[issue44869] MacOS Monterrey malloc issue

2021-08-11 Thread Eduardo Morales
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

[issue44869] MacOS Monterrey malloc issue

2021-08-08 Thread Eduardo Morales
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 <https://bugs.python.org/is

[issue44869] MacOS Monterrey malloc issue

2021-08-08 Thread Eduardo Morales
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 <https://bugs.python.org/is

[issue44869] MacOS Monterrey malloc issue

2021-08-08 Thread Eduardo Morales
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