| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
What exactly causes the AutoreleasePool to be freed when the Java object is garbage collected? It sounds like this is not happening for whatever reason.
On May 2, 2005, at 2:20 PM, String Larson wrote:
Thanks.
I had wrapped all my threads with pools (push/pop) just to try and see that was happening. I'm not getting the 'just leaking' messages any longer.
However, memory is not being released when the Java object containing NSImages is GC'd and/or the pool is released/popped.
I've been stripping things down - running a Java class w/o JBoss and as a single thread to eliminate variables. Still no luck.
Its behaving as if NSImage is leaking. It seems there is an OS thread (AppKit ?) that is alloc-ing NSViews and NSImageCacheViews w/o a pool in place these don't seem to get collected when the NSImage is GC'd.
I'm going to put together a simple working example that can be posted here.
Any detailed info on AppKit/etc. would be helpful/welcome.
Thanks.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden This email sent to email@hidden
| References: | |
| >Headless Cocoa/Java app - autorelease (From: String Larson <email@hidden>) | |
| >Re: Headless Cocoa/Java app - autorelease (From: Shawn Erickson <email@hidden>) | |
| >Re: Headless Cocoa/Java app - autorelease (From: String Larson <email@hidden>) | |
| >Re: Headless Cocoa/Java app - autorelease (From: John Stiles <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
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.