i have seen this happen while using some xtras that have memory leaks.
xml parser and ravjoystick, I think.
good luck.
-chris
Slava Paperno wrote:
I misstated the error message in my earlier email. It is actually:
"A fatal error has occurred. Director will quit now."
At 10:26 AM 12/2/2005, one of us wrote:
...but then again, there are times, where director chokes for no
apparent reason with the same result :-)
I'm seeing these incidents at the rate of about one every two full
days of work: "Director is completely out of resources... will quit
now," but then it always offers to save the current movie. I've never
been able to associate these situations with any events or actions.
I've been working with the same project for many months now, so it is
possible that my Lingo has a fatal flaw somewhere. Still, it appears
completely random and happens only after hours of work--it has never
happened soon after a Director restart and has never required a
machine restart.
I wonder how often this happens to other developers and what possible
reasons there may be for this?
I use Windows XP, SP2, fully upated, and the latest release of
Director MX 2004, a Dell tower, almost four years old, 1.7 GHz Pentium
Xeon, 2 GB of RAM, no sound card now (I use USB and Firewire audio
interfaces) but when I used SoundBlaster Live, I saw the same
behavior; Matrox Parhelia video card w/two displays.
Slava
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list,
email [email protected] (Problems, email
[EMAIL PROTECTED]). Lingo-L is for learning and helping with
programming Lingo. Thanks!]
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
