[issue1445] Major regression since 2.0 beta
New submission from Florian Apolloner <florian@apolloner.eu>: Alex asked me to open the bug, I am myself not 100% sure it's pypy's fault -- but I am somewhat out of debugging options. Django's testsuite gets a lot of memory allocation errors under pypy like: ====================================================================== ERROR: test_complex_app (admin_scripts.tests.ManageValidate) manage.py validate does not raise an ImportError validating a complex app with nested calls to load_app ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/florian/sources/django.git/tests/admin_scripts/tests.py", line 1073, in test_complex_app out, err = self.run_manage(args) File "/home/florian/sources/django.git/tests/admin_scripts/tests.py", line 176, in run_manage return self.run_test('./manage.py', args, settings_file) File "/home/florian/sources/django.git/tests/admin_scripts/tests.py", line 140, in run_test universal_newlines=True).communicate() File "/home/florian/sources/pypy-c-jit-63155-972e776a277f-linux64/lib-python/2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/home/florian/sources/pypy-c-jit-63155-972e776a277f-linux64/lib-python/2.7/subprocess.py", line 1147, in _execute_child self.pid = os.fork() OSError: [Errno 12] Cannot allocate memory This is on a 64 bit machine with 4 Gig of RAM, once in a while even oom_killer hits it… I am also seeing segfaults on the ci-server, but those appear to be fixed with the recent nightlies. ---------- messages: 5551 nosy: apollo13, pypy-issue priority: critical status: unread title: Major regression since 2.0 beta ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1445> ________________________________________
Fijal <fijall@gmail.com> added the comment: Try, as root: echo 1 > /proc/sys/vm/overcommit_memory or maybe 2, this should fix it another issue is why pypy eats so much RAM, but well. Another question ---------- nosy: +fijal status: unread -> chatting ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1445> ________________________________________
Armin Rigo <armin.rigo@gmail.com> added the comment: One clear cause of MemoryError is GCC 4.8, which we fixed it after beta2. Did you use GCC 4.8 to compile it? ---------- nosy: +arigo ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1445> ________________________________________
Florian Apolloner <florian@apolloner.eu> added the comment: Dunno, I was using your nightlies, so whatever you did use I used… ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1445> ________________________________________
Armin Rigo <armin.rigo@gmail.com> added the comment: Then the problem is different... ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1445> ________________________________________
mattip <matti.picus@gmail.com> added the comment: I have a ubuntu virtual machine with 2GB RAM and no swap. I cannot reproduce the report, even with a stock pypy 2.2.1: $ python -c "import sys;print sys.version" 2.7.3 (87aa9de10f9ca71da9ab4a3d53e0ba176b67d086, Nov 28 2013, 08:53:41) [PyPy 2.2.1 with GCC 4.8.2] $ git clone https://github.com/django/django.git $ cd django $ python setup.py install $ tests/runtests.py ... Ran 6849 tests in 570.670s FAILED (failures=2, errors=5, skipped=546, expected failures=8) None of the failing tests (nor errors) are out-of-memory errors ---------- nosy: +mattip ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1445> ________________________________________
participants (4)
-
Armin Rigo
-
Fijal
-
Florian Apolloner
-
mattip