[Python-Dev] Possible GIL/threading issue involving subprocess and PyMem_MALLOC... (original) (raw)
Antoine Pitrou solipsis at pitrou.net
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 PyMemMALLOC 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 PyMemMALLOC 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 ]