[Python-Dev] Possible GIL/threading issue involving subprocess and PyMem_MALLOC...
Antoine Pitrou
solipsis at pitrou.net
Fri Dec 21 10:43:11 CET 2012
More information about the Python-Dev mailing list
Fri Dec 21 10:43:11 CET 2012
- Previous message: [Python-Dev] Possible GIL/threading issue involving subprocess and PyMem_MALLOC...
- Next message: [Python-Dev] Possible GIL/threading issue involving subprocess and PyMem_MALLOC...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le Fri, 21 Dec 2012 09:31:44 +0000, Kristján Valur Jónsson <kristjan at ccpgames.com> a écrit : > I ran into this the other day. I had put in hooks in the > PyMem_MALLOC to track memory per tasklet, and it crashed in those > cases because it was being called without the GIL. My local patch > was simply to _not_ release the GIL. Clearly, calling PyMem_MALLOC > without the GIL is an API violation. Indeed, this deserves fixing. (it would be better to still release the GIL around the low-level I/O call, of course) Thanks Trent for finding this! Antoine.
- Previous message: [Python-Dev] Possible GIL/threading issue involving subprocess and PyMem_MALLOC...
- Next message: [Python-Dev] Possible GIL/threading issue involving subprocess and PyMem_MALLOC...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list