URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13705>
Summary: possible memory leak in setStringValue
Project: GNUstep
Submitted by: rmottola
Submitted on: Sun 07/10/2005 at 00:41
Category: Gui/AppKit
Severity: 3 - Normal
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
I found a possible memory leak in setStringValue.
Hunting down some excessive memory usage during file transfers in FTP.app (of
GAP project), I noticed that while on MacOSX the memory goes up and up during
a transfer but returns to the original value afte rthe transfer finished, on
GNUstep the usage remains high. Transferring another file makes memory usage
increase further.
Essentially the core is:
speedStr = [NSString alloc];
speedStr = [speedStr initWithFormat:@"%3.2fB/s", speed];
[infoSpeed setStringValue:speedStr];
[speedStr release];
now by commenting in and out code lines, I found that if the setStringValue
call is not done, memory usage doesn't increase inside the download loop.
It wonders me that such a call is memory expensive, but still, on osx the
memory is freed, on gnustep not and it leask as wild, thus I fear a bug like a
missing release.
I forgot,
IBOutlet NSTextField *infoSpeed;
Reproduceable on netbsd and linux.
maybe it is not possible to call setStringValue repeatedly for a text filed?
would be strange....
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13705>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
