Tcl Source Code

View Ticket
Login
Ticket UUID: 2043634
Title: 8.5.4rc0 mem leaks
Type: Bug Version: obsolete: 8.5.4
Submitter: pointsman Created on: 2008-08-09 00:18:16
Subsystem: 41. Memory Allocation Assigned To: dgp
Priority: 7 High Severity:
Status: Closed Last Modified: 2008-08-20 20:40:34
Resolution: None Closed By: dgp
    Closed on: 2008-08-20 13:40:34
Description:
With 8.5.4rc0, --enable-symbols --disable-threads, -DPURIFY added. If I run the test suite under valgrind (with proc exit args {} at the end) there's a lot of noise. 

It's clear to me, that this valgrind output isn't maximal
helpful. There are probably only a few spots, if ever, which may be used to write 'real' leaking scripts. Though, I can't show such a script atm. Anyway, memory hygiene of 8.5.4rc0 isn't as bright as it was in earlier versions.
User Comments: dgp added on 2008-08-20 20:40:34:
Logged In: YES 
user_id=80530
Originator: NO


time for testing RCs is past.

If there's still memleaks in
the 8.5.4 release, open a new
ticket.

dgp added on 2008-08-12 21:55:32:
Logged In: YES 
user_id=80530
Originator: NO


RC1 now available for testing.

andreas_kupries added on 2008-08-12 03:42:05:
Logged In: YES 
user_id=75003
Originator: NO


Ok, a fix was committed to the 8.5 branch.
Porting to 8.4 and 8.6 now.
Same test triggers.
Same fix works.
Committed.

It is unclear to me if I can close the bug now, or if there are other problems to handle, just by someone else?
Lowering prio. Unassigning.

msofer added on 2008-08-10 06:05:26:
Logged In: YES 
user_id=148712
Originator: NO

The script
while {1} {
catch {
proc p x {
set y [string tolower $x]
return "$x:$y"
}
procbodytest::proc t x p
} result
incr i
}

leaks a CmdFrame when sourced (but not when run from the command line), both in 8.5 and 8.6. The
stack trace is at http://paste.tclers.tk/1130, the growth can easily be seen in top.

pointsman added on 2008-08-09 07:18:17:

File Added - 287786: valgrind.out

Attachments: