Re: Release of NSData causes crash
Re: Release of NSData causes crash
- Subject: Re: Release of NSData causes crash
- From: Bill Bumgarner <email@hidden>
- Date: Tue, 2 May 2006 18:16:53 -0700
On May 2, 2006, at 6:06 PM, John Nairn wrote:
Yes, it works fine to release back in the method that owns it
(which it what I was doing), but in this case the NSData might be
from a large file (100's of MB) and I have been able to exhaust
virtual memory while reading such a file in a thread. I was
attempting to free some memory in the middle of the reading process
(reading is done in setRecordsFromString) once I was done with it
rather than waiting until the end and control is returned to the
owner of gedData.
There might be another problem causing virtual memory limits, but
this was one thing I thought I could try to see if it helped?
Hang on... so, you are reading data in one thread and processing the
data in another thread?
By moving the release from one method to the other -- there is no
concept of a method "owning" anything -- did you also move the
release from one thread to another?
The above paragraph parses as if there is considerably more
complexity than the code sample implies.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden