Re: crash in the carbon event loop

On Wed, Nov 11, 2009 at 5:57 PM, Emmanuel Quetelard
<[email protected]> wrote:
> Actually when I don't release  any event, the crash still there, so it can't be that (or there is something I didn't understand) . Can it be a release of something else than an event that could cause this crash?

Any time you have a memory management bug, it can manifest itself as
something else.  And since you didn't post your code or the backtrace,
there's really nothing more informative anyone can say.

Things to take away:

1) If you crash, it's usually because of an over-release.
2) You should be running the clang static analyzer frequently.
Especially after you crash.
3) If fixing the static analyzer's warnings doesn't help, and you
decide to post to a mailing list, you need to include the backtrace
and any code involved.

--Kyle Sluder