New submission from dktc <[email protected]>: I have a multi-processing, multi-threaded Django app that crashes when a secondary thread is trying to import a package that was not previously imported in the main thread.
The environment is the same as in https://bugs.pypy.org/issue1509 with PyPy 2.0.2. I suspect the root causes of the error might also be somehow connected. Strangely enough this error is quite fickle and only reproduces irregularly. The stacktrace simply shows that the error occurs on the "import" statement - ... my custom error message ... Traceback (most recent call last): ... my stack trace ... import mypackage RuntimeError: not holding the import lock Here is the error message that is urging me to report a bug - Fatal error in cpyext, CPython compatibility layer, calling PyEval_SaveThread Either report a bug or consider not using this particular extension <SystemError object at 0x1c31c98> RPython traceback: RPython traceback: File "pypy_interpreter_generator.c", line 2267, in portal_11 File "pypy_module_cpyext_api.c", line 35140, in PyEval_SaveThread File "rpython_jit_metainterp_warmstate.c", line 14489, in maybe_compile_and_run__star_4_1 File "rpython_jit_metainterp_warmstate.c", line 21788, in execute_assembler__star_3_7 File "rpython_jit_metainterp_blackhole.c", line 874, in _run_forever File "rpython_jit_metainterp_blackhole.c", line 3301, in _handle_jitexception Fatal RPython error: AssertionError File "rpython_jit_metainterp_compile.c", line 23635, in ResumeGuardDescr_handle_fail Fatal RPython error: AssertionError (7455) Child died from signal 6 with code 0 ---------- messages: 5833 nosy: pypy-issue priority: bug release: 2.0 status: unread title: import lock problem crashes PyPy ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1512> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-issue
