Re: Threads again: NSData leaking (using dataWithContentsOfURL)
Re: Threads again: NSData leaking (using dataWithContentsOfURL)
- Subject: Re: Threads again: NSData leaking (using dataWithContentsOfURL)
- From: BOGUS BOGUS <email@hidden>
- Date: Tue, 10 Feb 2004 06:54:19 -0800
On Feb 10, 2004, at 1:38 AM, Stefan Pantke wrote:
In Apple's OS X 10.2 release notes, I found some hints on
NSData fixed leaks/problems.
Since I work on 10.3.2, things should work fine.
Any help greatly welcome.
Am 09.02.2004 um 20:51 schrieb Stefan Pantke:
As soon as I perform
downloadedData = [NSData
dataWithContentsOfURL:urlForDownload];
all workers mutate to memory consumers - the node count reported from
leaks
jumps from 20000 to 88000.
Since URLWithString is a convenience method, it should autorelease
it's memory.
Thus, it SHOULD be released, since the worker's main loop releases
it's local
AutoreleasePool at the end of the loop, which has been allocated at
the beginning
of the loop.
This assumption may be the problem. I think the autorelease pool is
cleaned up only if a UI event is processed by the runloop. Try posting
an event periodically in your thread and see if it fixes the problem.
The downloadedData is not used by any other part of code, not is it
used for
diplay purposes, e.g.
Baskaran Subramaniam
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.