Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Help diagnosing memory problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help diagnosing memory problem

Subject: Re: Help diagnosing memory problem
From: Tom Davies <email@hidden>
Date: Fri, 7 Dec 2007 17:28:58 +1100


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


Follow-Ups:

Re: Help diagnosing memory problem
From: John Stiles <email@hidden>


References:  
  >Help diagnosing memory problem (From: Tom Davies <email@hidden>)
  >Re: Help diagnosing memory problem (From: Rob Keniger <email@hidden>)




Prev by Date:
How to Implement File Encryption with SSCrypto?

Next by Date:
Re: Enable Debug Menu for Webkit based cocoa application

Previous by thread:
Re: Help diagnosing memory problem

Next by thread:
Re: Help diagnosing memory problem

Index(es):

Date
Thread