Re: Crash on quit - AudioOutputUnit app
Re: Crash on quit - AudioOutputUnit app
- Subject: Re: Crash on quit - AudioOutputUnit app
- From: Chris Reed <email@hidden>
- Date: Sun, 8 Jun 2003 16:21:09 -0500
On Saturday, Jun 7, 2003, at 10:44 US/Central, Roni Music wrote:
Thread 3 is my render thread that is for sure destroyed before main
exits. Does this mean that it crashed inside the main program
thread
anyway?
all the backtrace tells us of interest is that at global destruction
time, memory has been corrupted. Use the standard techniques for
debugging memory smashers...
My main concern is if that could be caused by running the software on
dual processor machine?
It doesn't show up on my single processor machine.
There are most definitely memory stompers that appear only on dual
processor machines and not on single processors. I've seen it with my
code, as well as other people's.
Usually it is more of a threading issue (non-thread-safe code) than a
classic memory stomper like a double-freed pointer or something.
-chris
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.