It uses subprocess, but you need to quit pypy (so run this with --source and then make separately) for memory to be reclaimed
On Sun, Mar 6, 2016 at 11:01 PM, Matti Picus <matti.pi...@gmail.com> wrote: > > > On 06/03/16 12:04, Yury V. Zaytsev wrote: > > On Sat, 5 Mar 2016, Yury V. Zaytsev wrote: > > So, it looks like with PyPy 5.0.0 the problem is exactly the same as with > the previous version. The translation goes through (and possibily faster / > uses less memory, I didn't check), but the compilation bails out with a > `MemoryError` at `buffer.append(fh.read())`: > > http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/2266/steps/translate/logs/stdio > > In the mean time, I rolled back to PyPy 2.5.1 on the build slave. Oh wait, I > meant to say build follower. Sorry about this. > > I watched the compile part of translation in a system monitor on a local VM. > Using the pypy 5.0 release, during compilation there is a single pypy.exe > process requiring about 2.8GB of memory. At some point, toward the end of > compiling the 1000+ source files (perhaps during link?) memory consumption > jumps way up, trying to access at least another GB of memory, at which point > the virtual machine complains and the pypy.exe crashes. Any ideas? I thought > the compile step uses multiprocessing to run in a seperate process, but it > seems I am wrong. > Matti > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
