Hi Ronny, hi Roger, On Wed, Apr 4, 2012 at 09:27, Ronny Pfannschmidt <ronny.pfannschm...@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. _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
