New submission from tonypypy <antoun.kanawati@gmail.com>: While trying out latest pypy, I got consistent core dumps on one program; here's the stack trace from 2.0.2; I had the same problem yesterday with 2.0.1, but didn't get a change to generate the trace. Pypy 2.0.2; built from source; installed with virtualenv: $ ./rpython/bin/rpython -Ojit pypy/goal/targetpypystandalone.py $ virtualenv -p $PWD/pypy-c /opt/pypy-2.0.2 $ cd ~/myproject $ . /opt/pypy-2.0.2/bin/activate (pypy-2.0.2)$ pypy bin/program.py < data.json ................................................................................ ... ................................................................................ ... ....................................................zsh: segmentation fault (core dumped) Trying again with /usr/bin/time: 2.22user 0.14system 0:03.03elapsed 77%CPU (0avgtext+0avgdata 159568maxresident)k 0inputs+0outputs (0major+53786minor)pagefaults 0swaps Each period is printed at the end of a function call that creates a few thousand sets, frozensets, tuples, lists. The program is purely sequential, and pure python (no C/C++ parts). I use cPickle instead of pickle. --------------------------------------------------------------------- No problem pypy 1.9. Haven't tried stock python (too slow for this). * Environment: Fedora core 17; 8GB RAM; intel i7 $ uname -a Linux lenovo-t420s 3.8.12-100.fc17.x86_64 #1 SMP Wed May 8 15:36:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # This pypy does not dump core. $ pypy -V Python 2.7.2 (341e1e3821fff77db3bb5cdb7a4851626298c44e, Jun 18 2012, 13:48:33) [PyPy 1.9.0 with GCC 4.7.0] ---------- messages: 5759 nosy: pypy-issue, tonypypy priority: critical status: unread title: pypy 2.0.x crash (stack trace included) ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1496> ________________________________________