New submission from dktc <[email protected]>: I've discovered some really strange behavior with PyPy 2.0.2. Not familiar enough with PyPy / eventlet architecture to trace this bug further, but can report the conditions causing it:
1) Install Spawning master ( https://github.com/rtyler/Spawning/ ) with eventlet 0.12.1 2) Create a sample Django 1.5 app and set it up as WSGI under Spawning 3) Start Spawning with 3 processes, 4 threads and --sysinfo option 4) Open http://domain.com/_sysinfo to see that --sysinfo interceptor works fine 5) Open any regular page from Django app, reload it several times 6) Try to open http://domain.com/_sysinfo again and note that it times out / crashes 7) Try steps 4-6 a few more times if the crash does not occur immediately 8) Note that if you do a process listing "ps aux" there will be more child processes than expected 9) Note that killing parent/controller process after crash won't terminate the children This behavior does not happen on CPython 2.7.4 - all pages load correctly, the number of children always stays as specified and terminating the controller causes termination of all children. There have to be some bugs in PyPy to be causing this behavior... ---------- messages: 5823 nosy: pypy-issue priority: bug release: 2.0 status: unread title: weird crashes with eventlet/spawning ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1509> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-issue
