[Python-bugs-list] [ python-Bugs-485145 ] memory leak in test_unicode

[noreply@sourceforge.net]

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

Category: Python Interpreter Core
Group: Python 2.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Neal Norwitz (nnorwitz)
Assigned to: Barry Warsaw (bwarsaw)
Summary: memory leak in test_unicode

Initial Comment:
test_unicode leaks memory
see attached file for details

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

>Comment By: Neal Norwitz (nnorwitz)
Date: 2001-12-06 12:29

Message:
Logged In: YES 
user_id=33168

This leak was plugged with the unicode fix for #489669
"memory leak in test_descr (unicode)"

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

Comment By: M.-A. Lemburg (lemburg)
Date: 2001-12-06 04:03

Message:
Logged In: YES 
user_id=38388

Indeed, if I comment out the section "Testing builtin unicode()..." the leak goes away. Barry, that's where you 
should start looking !

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

Comment By: M.-A. Lemburg (lemburg)
Date: 2001-12-06 03:39

Message:
Logged In: YES 
user_id=38388

I've done some tests and found that the leaks have to be somewhere in test_unicode.py below the line "Testing 
builtin unicode()...".

Since the code immediately below that line uses type subclassing I guess that the new type system could have 
something to do with the leakage.

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

Comment By: M.-A. Lemburg (lemburg)
Date: 2001-12-06 01:02

Message:
Logged In: YES 
user_id=38388

Note that the "leak" could be caused the fact that Unicode shares length 1 Unicode strings in the Latin-1 range.

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

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

Message:
Logged In: YES 
user_id=31435

Assigned to Barry.

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

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