Re: Help diagnosing memory problem
Re: Help diagnosing memory problem
- Subject: Re: Help diagnosing memory problem
- From: John Stiles <email@hidden>
- Date: Fri, 07 Dec 2007 08:39:07 -0800
Absolutely that is worth a radar!
I've filed radars for much smaller issues :)
Tom Davies wrote:
On 04/12/2007, at 7:00 PM, Rob Keniger wrote:
On 04/12/2007, at 3:18 PM, Tom Davies wrote:
My interpretation of the message is that the finalize method of
NSCFURLProtocolBridge is somehow causing an object which has already
been garbage collected to be referenced again. Is that correct? What
procedure should I follow for tracking the cause down?
I'm also getting this message in a GC app that uses a custom
NSURLProtocol. So far I've had no luck tracking down the cause either.
I can reproduce this problem with Apple's SpecialPictureProtocol
example, just by changing the app to gc-required and clean building.
Is that worth a bug report to Apple?
Tom
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden