[Apocalypse]

Hello,

Some of the work I have been doing in the last day has led my system to an odd sort of freeze twice. Since I have had amazing uptime until yesterday, I was wondering if anyone could shed some light on my problem.

Looking in the System Log, I find these entries whenever one of these freezes occurs:
<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>Sep <font color = blue>12</font> <font color = blue>17</font>:<font color = blue>29</font>:<font color = blue>04</font> localhost mach_kernel: LLEventQueue overflow.
Sep <font color = blue>12</font> <font color = blue>17</font>:<font color = blue>30</font>:<font color = blue>18</font> localhost mach_kernel: IOHIDSystem: postEvent LLEventQueue overflow.</font>[/code]

I don't know what has been causing it but the most recent addition to the program that this crashes while testing is sounds. I am wondering if there is some issue with the NSSound API in Cocoa. I have also noticed recent problems with one of my OpenGL views since the introduction of sound.

Note, however, that this crash does not occur EVERY TIME I run the program. Unfortunately, I can't figure out why this is happening.

Pertinent information: One sound is looping when this happens, one OpenGL view is being re-drawn every 0.05 seconds and the other OpenGL view just received a mouse click.

Any help would be great,
Jeff.

[parallax]

Apoc: A while ago, I was fooling around with CoreAudio, trying to make some synthesizer program. Accidentally, I moved my slider up to a very high value, and apparently it sent CoreAudio some negative number. The -whole- computer froze in a weird crash that I haven't seen since OS 9.

Heh, I stopped working with sound after that.

[Apocalypse]

Actually, I think that I found the cause about an hour ago.

I had recently added a second thread to my program when this started to happen (I had made a ton of other changes, too, so I figured this was not the obvious problem). However, I also noticed that sometimes one of my OpenGLViews would appear with extra extraneous shapes in it. I then remembered what some of the components of this other thread would do (things that I had neglected before). It turns out that one of the last calls before the thread exits is "setNeedsDisplay:YES" to the OpenGLView exhibiting the odd behavior. Once I removed the detach thread call, everything became fine.

Also, in the kernel panic module trace, the com.apple.ATIRage128 kernel extension was loaded. Given that I am already using to OpenGLViews on a low-end card with the not-always-thread-safe AppKit, I should not have been surprised when weird freezes and kernel panics occurred.

Just goes to show that thread-safety is an important issue to keep in mind.

Fun stuff, eh?
Jeff.