[issue8176] Interpreter crash with "double free or corruption" message

Christian Heimes added the comment: I'm closing the bug because it hasn't seen any activity in the past 2.5 years. -- nosy: +christian.heimes status: open -> closed ___ Python tracker ___

[issue8176] Interpreter crash with "double free or corruption" message

Antoine Pitrou added the comment: I wouldn't be surprised if the crash was related to some concurrency issues during shutdown. Other (Python or not Python) threads can continue running while the main thread is running Py_Finalize; this might be the reason; or perhaps some extension modules do

[issue8176] Interpreter crash with "double free or corruption" message

Alexander Belopolsky added the comment: Victor, I was thinking about pointing the OP to your faulthandler module, but decided not to because in the failing thread python has already finished execution and most of finalization. It is very unlikely that faulthandler will be helpful in this sc

[issue8176] Interpreter crash with "double free or corruption" message

STINNER Victor added the comment: If you are still able to reproduce the bug, you may try the following module to get a backtrace: https://github.com/haypo/faulthandler/ -- status: pending -> open ___ Python tracker

[issue8176] Interpreter crash with "double free or corruption" message

Alexander Belopolsky added the comment: It looks like the bug cannot be reproduced anymore. Since it was discovered using a python instance with third-party extension modules, it may not even be a python bug to begin with. -- assignee: -> belopolsky nosy: +belopolsky -Alexander.Belo

[issue8176] Interpreter crash with "double free or corruption" message

Changes by Alexander Belopolsky : Removed file: http://bugs.python.org/file16615/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8176] Interpreter crash with "double free or corruption" message

Changes by Alexander Belopolsky : Removed file: http://bugs.python.org/file16584/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8176] Interpreter crash with "double free or corruption" message

Carlos Ribeiro added the comment: Thanks for investigating! I'll keep watching. I'm currently developing a small Django app, and the crash happened during one of the automatic reloads that the development server do whenever a source code file changes. The problem is that I probably ran through

[issue8176] Interpreter crash with "double free or corruption" message

Alexander Belopolsky added the comment: Clearly not enough information, but I have a few observations: 1. Clearly the crash occurs on exit (in Py_Finalize) during a module cleanup. (Unfortunately it looks like a non-debug build of Python was used so figuring out which module is involved may

[issue8176] Interpreter crash with "double free or corruption" message

Carlos Ribeiro added the comment: I know I have little information but unfortunately I couldn't reproduce the crash. Seems like a racing condition or something similar. I'll see what I can do about it. On Fri, Mar 19, 2010 at 07:46, STINNER Victor wrote: > > STINNER Victor added the comment:

[issue8176] Interpreter crash with "double free or corruption" message

STINNER Victor added the comment: Python was displaying an error: did you saw the error? I don't know where Django logs stderr. Could you also run Python in verbose mode? Set PYTHONVERBOSE=2 environment variable. It should write useful informations before the crash. -- nosy: +haypo

[issue8176] Interpreter crash with "double free or corruption" message

New submission from Carlos Ribeiro : I was running Django in development mode (python manage.py runserver 0.0.0.0:8002). I saved a python source file; Django automatically detected the change and reloaded the module (that's the usual behavior). Then a backtrace from glibc appeared in the middl