[pypy-issue] [issue878] too many open files

Armin Rigo tracker at bugs.pypy.org
Fri Apr 11 10:55:56 CEST 2014

Armin Rigo <armin.rigo at gmail.com> added the comment:

VYSE: yes, that's possible, but that might be a very bad idea in some cases.  It
means that if your program leaks FDs heavily, then it would work, but force a
complete GC cycle every n'th leaked FDs.  The value of n is a constant, but the
program can take an arbitrary amount of memory, which makes a complete GC cycle
arbitrarily long.  The end result is that PyPy would spend an arbitrarily large
fraction of its run time in the GC --- slowing down the actual execution, not by
10% nor 100% nor 1000% but by essentially any factor.

I think it's a better idea to go to the individual projects and tell them that
they need to close their open files in order to run on any non-CPython
implementation of Python.

nosy: +arigo

PyPy bug tracker <tracker at bugs.pypy.org>

More information about the pypy-issue mailing list