pure virtual method called

Rxke · Post by **Rxke** » Thu Feb 23, 2006 8:57 am

Oh, and I had Gmail Notifier running too, which occasionally makes a sound when emails come in (and temporarily 'micro'freezes my old G3 when checking stuff, incoming new emails or not)
But recently, I switched it off, just because of the freezes.

Hmmm... The plot thickening?

JensAyton · Post by **JensAyton** » Thu Feb 23, 2006 9:25 am

Other sound code, be it the speech manager or other apps, really really should not be able to have any impact on the sound bug.

Hmm. “Current context?” What exactly is the error message you lot are getting?

Rxke · Post by **Rxke** » Thu Feb 23, 2006 9:36 am

(goes through logs....)

Ah:

OOCASoundMixer: failed to connect channel <OOCASoundChannel 0x1392c50>{ID=8, state=stopped, sound=<OOCABufferedSound 0x4e57d80>{"warning.ogg"}}, error = kAudioUnitErr_CannotDoInCurrentContext/kAUGraphErr_CannotDoInCurrentContext/kAUGraphErr_CannotDoInCurrentContext.

(Whew, buried deep, been quite awhile since it happened (yay!)

(Edit: that's when it hangs, not the 'pure virtual method called' sudden exit of Oolite.

Murgh · Post by **Murgh** » Thu Feb 23, 2006 10:10 am

too deep in my logs to search. instead I tried to reproduce it and couldn't after near 30 mins of appplying all the tricks I thought I knew.

hey, maybe it's gone (inshAllah!)

aegidian · Post by **aegidian** » Thu Mar 02, 2006 10:31 am

I've just started getting this problem too.

Code: Select all

pure virtual method called

and a sudden exit from Oolite (no crash result - presumably exit(0) is being called).
It seems to occur when iTunes changes track, which makes me suspect a bug in either Groolite or Growl itself.

JensAyton · Post by **JensAyton** » Fri Mar 10, 2006 2:14 pm

Bah, I was liking the speech synthesis thing. Groolite doesn’t do C++, and I don’t see how Growl could crash Oolite since they only communicate through notifications and distributed objects.

aegidian · Post by **aegidian** » Fri Apr 28, 2006 9:52 am

It's definitely Growl. When this happens it always occurs on a track change, and it can happen at any point in Oolite.

I have to say the method stumps me too, but the association is 100%.

JensAyton · Post by **JensAyton** » Fri Apr 28, 2006 2:24 pm

If you're getting it consistentlyish, could you try to get a backtrace? (Run under debugger, open debugger console, ”break abort”.) It’d be nice to have some idea of what context this is happening in.

Rxke · Post by **Rxke** » Fri Apr 28, 2006 2:43 pm

I had it happen w/o Growl, so it won't be only Growl causing this, I'm pretty sure it's the voice-synth. Ever since switching it off, crashing stopped.

aegidian · Post by **aegidian** » Fri Apr 28, 2006 3:29 pm

Voice synth would make sense too. Since I have the voice announce Growl messages in Oolite. Okay - not definitely Growl.

It'd be a shame to cut out the voice synth because of this - perhaps I can use one of those Open Source voice synths instead.