New issue 1926: PyPy STM segfault with short transactions https://bitbucket.org/pypy/pypy/issue/1926/pypy-stm-segfault-with-short-transactions
Konstantin Lopuhin: Steps to reproduce are the same as in #1918: ``` hg clone ssh://[email protected]/kostialopuhin/tornado-stm-bench cd tornado-stm-bench hg up a038bf99de71 virtualenv env -p pypy-c-r74378-74379-stm-jit source env/bin/activate pip install -r requirements.txt ./primes.py 4 ``` the only difference is that now to run benchmark do ``` siege -c 20 -t 20s http://localhost:8888/500 ``` the difference is that here transactions are much shorter (primes up to 500 instead of 10000). This is not 100% reliable way to get a segfault, but I get it more often than not. I can try with a newer build _______________________________________________ pypy-issue mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-issue
