[Python-bugs-list] [ python-Bugs-485150 ] memory leak from marshal.c (test_email)

[noreply@sourceforge.net]

Bugs item #485150, was opened at 2001-11-24 11:39
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=485150&group_id=5470

Category: Python Interpreter Core
Group: Python 2.2
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Neal Norwitz (nnorwitz)
Assigned to: Guido van Rossum (gvanrossum)
Summary: memory leak from marshal.c (test_email)

Initial Comment:
marshal.c seems to be the culprit in leaking data
from running test_email
see attached file for details

----------------------------------------------------------------------

>Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-07 08:44

Message:
Logged In: YES 
user_id=6380

According to mail from Neal, this is fixed -- probably by
some other leak fix.

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-06 19:43

Message:
Logged In: YES 
user_id=6380

I can't get any of the test suites from test_email.py to
grow when I place them in a loop. Maybe this is another
one-time leak? Or maybe the leak is related to import?
(Historically, there have often been small one-time leaks in
import -- these are hard to find but also relatively
unimportant, since one rarely re-imports modules over and
over.) If that's the case, maybe it's possible to construct
a test case out of a small module that's reloaded over and
over?

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-06 14:12

Message:
Logged In: YES 
user_id=6380

It's not marshal's fault -- we see this all the time when a
constant loaded from a .pyc file is leaked by some code that
gets it passed in as an argument.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-11-27 12:04

Message:
Logged In: YES 
user_id=31435

Assigned to Barry.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=485150&group_id=5470