Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: StackOverflowError (Resolved)



On Thu, 28 Jul 2005, Scott Ellsworth wrote:


On Jul 28, 2005, at 7:16 PM, Bjorn Roche wrote:

I also wanted to reply to one person in particular who pointed out that it's a good idea to set all references to null when disposing a window. My reading of this:


http://developer.apple.com/releasenotes/Java/Java142RN/ OutstandingIssues/chapter_4_section_3.html

Is that that's not just a good habit, but rather imperative on the Mac.

I would suspect based on the phrasing that the leak happens regardless of whether you null out your components. ObjectAlloc or Shark might have more info.

Yes, my impression is also that some sort of leak is inevitable. But since the window remains un-garbage collected, it seems likely that any references that the window holds will also be un-garbage collected (since they are all reachable through the window). If that is the case, releasing references on final window close will reduce the impact of apple's leak, because at least the other objects can be garbage collected.


	bjorn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden
References: 
 >Re: StackOverflowError (From: Greg Guerin <email@hidden>)
 >Re: StackOverflowError (Resolved) (From: Bjorn Roche <email@hidden>)
 >Re: StackOverflowError (Resolved) (From: Scott Ellsworth <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.