On Aug 4, 2009, at 18:12, dp wrote:
I recently updated some older code and converted to GC in the
process. Most of the time, things run fine. But every now and then I
seem to run into a CFRelease and/or a finalize down in system
libraries or Apple Frameworks. The ImageIO framework and
CFDateFormatter seem to be the culprits in some cases. How do I best
go about debugging these and/or working around them? Are these bugs
in the frameworks or just a GC issue I need to do something about?
Crash stacks below.
Thread 1 Crashed:
0 com.apple.ImageIO.framework 0x0396c6e4
jp2_family_src::close() + 10
1 com.apple.ImageIO.framework 0x0396c67a
_cg_JP2TearDownDecompressor + 28
2 com.apple.ImageIO.framework 0x0396c64f JP2ReleaseInfoCallback
+ 21
3 com.apple.Foundation 0x01a95a81 -[NSCFType finalize] +
49
4 libobjc.A.dylib 0x0087c6b6 finalizeOneObject + 56
What's the actual crash? Was it an exception? A signal? You should
check in the console log to see if there's any useful information there.
If an object is being finalized at the time of the crash, it's likely
you're failing to keep a strong reference to an object that you're
responsible for keeping alive. For example, something that was
previously being kept alive long enough by an autorelease (without any
explicit reference in your stack, global or instance variables) could
now be collected much earlier.
It's also possible that something that was thread-safe before (or
whose thread safety didn't matter) is now unsafe because of the
garbage collector thread.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
