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