Charles-François Natali <neolo...@free.fr> added the comment: This makes sense. I was suspecting a system limit exhaustion, maybe OOM or maximum number of threads, something like that. But at least on Linux, in OOM condition, the process would either get nuked by the OOM-killer, or pthread_create would bail out with ENOMEM (when allocating the stack for example), so we would be able to - somewhat - catch the error and get an exception (well, OOM condition is also often a sort of "undefined behaviour", so we can't really make a guarantee on the state of the interpreter when it's hit). Out of curioisity, could you try the attached test to see how it behaves on your VM? Usage: ./test_thread_oom <number of threads to create> On Linux it fails with ENOMEM "Resource temporarily unavailable".
---------- Added file: http://bugs.python.org/file21998/test_thread_oom.c _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12071> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
