RE: Shockwave can be brought to a state where playingmultiple sound channels at once cr

Good point. I haven't been able to repro this at all in the
IDE, but
I've seen it way too many times in the browser :(

Although it seems to be happening on an increasing number of
systems
(I'm sure it was a rare occurrence just a few years ago), it
doesn't
happen on all of them.

JeffM.

-----Original Message-----
From: dirgames-l-bouncesnuttybar.drama.uga.edu
[mailto:dirgames-l-bouncesnuttybar.drama.uga.edu] On
Behalf Of Lucas
Meijer
Sent: Monday, January 22, 2007 9:43 AM
To: Director - Shockwave - and Flash Game Production
Subject: Re: [dirGames-L] Shockwave can be brought to a
state where
playingmultiple sound channels at once crashes the plugin.

Hey Toni,

Shockwave crashing the browser when "doing things with
audio" is a long 
outstanding bug that has caused a lot of
people a lot of grief..  You could ask Simeon to vent his
frustrations, 
it's one of his favorite topics 

It is not yet fixed, and I do not get the feeling it has
been getting a 
lot of attention from macromedia/adobe.

In some setups it seems to happen a lot more frequent than
in others. 
Exactly what makes it happen is unknown, which
I guess makes it hard for adobe to fix it.

If this is the same thing you're expiriencing I'm not sure,
as you're 
the first one to report being able to reproduce it in
authoring

> Only thing we did find out is that the crash didn't
seem to occur 
> immediately on playback, but later in the frame when
updating one of 
> the sprites in the before-mentioned animations. (Can we
trust the 
> debugger on this? Is the call stack always correct?)
I have never seen the "call stack" to be
incorrect. It has always been 
correct for me, and I've done plenty of weird stuff with it
(mostly 
across miaw's) to make it go nuts.   What is often incorrect
is the line

you get shown by the debugger. If you want to be sure you're
looking at 
the line that is causing the problem, you should go one
level up in the 
callstack, and then go one level down again. That will
always result in 
the debug window showing you the correct line where the
problem
occurred.

When you say "crash" what do you mean?   Most of
the time developers use

"crash" when the director application exits due to
a fault.
You mention you are able to open the debugger, which sounds
this might 
be a scripterror?

Bye, Lucas
_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l


_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l