• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • 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: Rob Keniger <email@hidden>
  • Date: Tue, 4 Dec 2007 18:00:30 +1000


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.

--
Rob Keniger

_______________________________________________

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: Tom Davies <email@hidden>
References: 
 >Help diagnosing memory problem (From: Tom Davies <email@hidden>)

  • Prev by Date: Multithreaded NSView:setNeedsDisplay:
  • Next by Date: Re: Multithreaded NSView:setNeedsDisplay:
  • Previous by thread: Help diagnosing memory problem
  • Next by thread: Re: Help diagnosing memory problem
  • Index(es):
    • Date
    • Thread