On Sep 7, 2009, at 3:35 PM, Andrew Madsen wrote:
My app doesn't crash, and everything seems to work OK, but I'm
trying to figure out what this means. This is my first garbage
collected app, so I'm guessing there's something about the
intricacies of actually using garbage collection that I'm missing.
Any pointers?
Yes. File a bug with pretty much exactly what you posted to cocoa-dev.
When an application causes something to happen on a thread that GC
needs to be aware of, but that thread is not registered with the
collector, the collector will implicitly register the thread while
spewing a note to the console.
As Nick said, the behavior change between Leopard and Snow Leopard was
to actually log when this happens. In Leopard, the collector just
registered the thread, didn't tell you that it registered the thread,
and everything kept working just fine.
The behavior was changed because some developers were surprised to
find collector activity on their threads. Thus, the collector now
logs to mitigate surprise. (Of course, some developers were then
surprised by the log message. "But... but... but... my code cannot
possibly run under the garbage collector!!", they said. "Well...
that's funny... your code has been running under the garbage collector
for 18 months and you only noticed it when the collector started
telling you. Are you saying your code has been broken for all of that
time?", was the response.)
As Nick said, as well, if your code is spawning the thread, call
objc_registerThreadWithCollector(). If Audio Queue Services entirely
controls that particular backtrace, then file a bug via http://bugreport.apple.com/
as mentioned above.
b.bum
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
