pypy MemoryError crash
Hello all. A bug in a python application of mine resulted in this pypy crash: RPython traceback: File "translator_goal_targetpypystandalone.c", line 1033, in entry_point File "interpreter_function.c", line 1017, in funccall__star_1 File "interpreter_function.c", line 1046, in funccall__star_1 File "rpython_memory_gc_minimark.c", line 2512, in MiniMarkGC_collect_and_rese rve File "rpython_memory_gc_minimark.c", line 2216, in MiniMarkGC_minor_collection File "rpython_memory_gc_minimark.c", line 4503, in MiniMarkGC_collect_oldrefs_ to_nursery File "rpython_memory_gc_base.c", line 1714, in trace___trace_drag_out File "rpython_memory_gc_minimarkpage.c", line 214, in ArenaCollection_malloc File "rpython_memory_gc_minimarkpage.c", line 532, in ArenaCollection_allocate _new_page File "rpython_memory_gc_minimarkpage.c", line 728, in ArenaCollection_allocate _new_arena Fatal RPython error: MemoryError This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. At first I thought it was pypy reporting that the PPM compressor had ran out of memory, and simply didn't report the app's stack frames. But I've since come to realize that normally pypy does report a MemoryError and the stack frames involved, just like Python, and that this case was instead a RPython crash. I'm hoping the above stack trace from pypy is enough of a clue.
pypy -v Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 18:31:47) [PyPy 1.8.0 with MSC v.1500 32 bit] on win32
-Roger
Hello Roger, thanks for the initial report, but we could use some more information on what your program is doing (a rpython traceback is simply not enough of a clue to guess the problem) also it would be helpful, if you tried if the code works correct on a nightly build. Since you run on windows, also try on a linux to rule out platform issues. -- Ronny On 04/04/2012 02:14 AM, Roger Flores wrote:
Hello all. A bug in a python application of mine resulted in this pypy crash:
RPython traceback: File "translator_goal_targetpypystandalone.c", line 1033, in entry_point File "interpreter_function.c", line 1017, in funccall__star_1 File "interpreter_function.c", line 1046, in funccall__star_1 File "rpython_memory_gc_minimark.c", line 2512, in MiniMarkGC_collect_and_rese rve File "rpython_memory_gc_minimark.c", line 2216, in MiniMarkGC_minor_collection
File "rpython_memory_gc_minimark.c", line 4503, in MiniMarkGC_collect_oldrefs_ to_nursery File "rpython_memory_gc_base.c", line 1714, in trace___trace_drag_out File "rpython_memory_gc_minimarkpage.c", line 214, in ArenaCollection_malloc File "rpython_memory_gc_minimarkpage.c", line 532, in ArenaCollection_allocate _new_page File "rpython_memory_gc_minimarkpage.c", line 728, in ArenaCollection_allocate _new_arena Fatal RPython error: MemoryError
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
At first I thought it was pypy reporting that the PPM compressor had ran out of memory, and simply didn't report the app's stack frames. But I've since come to realize that normally pypy does report a MemoryError and the stack frames involved, just like Python, and that this case was instead a RPython crash.
I'm hoping the above stack trace from pypy is enough of a clue.
pypy -v Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 18:31:47) [PyPy 1.8.0 with MSC v.1500 32 bit] on win32
-Roger
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Hi Ronny, hi Roger, On Wed, Apr 4, 2012 at 09:27, Ronny Pfannschmidt <Ronny.Pfannschmidt@gmx.de> wrote:
thanks for the initial report, but we could use some more information on what your program is doing (a rpython traceback is simply not enough of a clue to guess the problem)
Indeed, we would need to know more. Normally, the RPython MemoryError is caught and turned into a Python-level MemoryError at some point. But according to the traceback the interpreter is not running any Python code at this point. It is either a corner case, or a real bug, depending on how your Python code looks like. It may also mean that you're running with a too strict memory restriction (with the environment variable PYPY_GC_MAX=value too small). A bientôt, Armin.
participants (3)
-
Armin Rigo -
Roger Flores -
Ronny Pfannschmidt