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

Showing content from https://mail.python.org/pipermail/python-dev/2005-November/058239.html below:

[Python-Dev] ast status, memory leaks, etc

• Previous message: [Python-Dev] ast status, memory leaks, etc
• Next message: [Python-Dev] Event loops, PyOS_InputHook, and Tkinter
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Neal Norwitz wrote:
> I still think the total references at the end of a test run are high,
> 342291.  I don't have anything to base this number on.  Some strategic
> interning should help this number go down a bit.  I suppose I
> shouldn't worry much since these references don't seem to become
> actual memory leaks.

You could try to classify the objects remaining, counting them
by type. Perhaps selectively clearing out sys.modules to what
it is after startup might also give insights.

Regards,
Martin

• Previous message: [Python-Dev] ast status, memory leaks, etc
• Next message: [Python-Dev] Event loops, PyOS_InputHook, and Tkinter
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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