A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2001-February/013070.html below:

[Python-Dev] compile leaks memory. lots of memory.

[Python-Dev] compile leaks memory. lots of memory. [Python-Dev] compile leaks memory. lots of memory.Jeremy Hylton jeremy@alum.mit.edu
Wed, 21 Feb 2001 16:10:15 -0500 (EST)
>>>>> "BAW" == Barry A Warsaw <barry@digicool.com> writes:

>>>>> "FL" == Fredrik Lundh <fredrik@effbot.org> writes:

  FL> while 1: compile("print 'hello'\n", "<string>", "exec")

  FL> current CVS leaks just over 1k per call to compile.
  FL> 1.5.2 and 2.0 doesn't leak a byte.

  FL> make the script a little more complex, and it leaks even more
  FL> (4k for a small function, 650k for Tkinter.py, etc).

  BAW> I have plans to spend a fair bit of time running memory/leak
  BAW> analysis over Python after the conference.  I'm kind of waiting
  BAW> until we enter beta, i.e. feature freeze.

It would be helpful to get some analysis on this known problem before
the beta release.

Jeremy



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4