Groups | Blog | Home
all groups > flash (macromedia) > january 2004 >

flash (macromedia) : Flash MX freezes constantly


Tom Unger
1/25/2004 8:44:23 PM
phlesch;
Where are you finding a download of the flashmx trial? It seems odd that
there would still be a legitimate trial copy available for download since
the application is no longer being sold by MM... -Tom Unger

phlesch
1/25/2004 11:50:50 PM
I have installed the trial version of MX (not MX 2004) on the following system:

dual 800MHz P3
800MB RAM
Windows NT 4.0 Service Pack 6a
more than 500MB of free space on C drive

within a few minutes of starting Flash one of the following happens:
- Flash freezes when I open a .fla file (Task Manager identifies it as "not responding", when I end the task a temporary file is created which cannot be deleted until reboot).
- if I have a .fla file open and I'm using the "Lessons" workfiles as well (in a Flash Player window), Flash freezes.
- less frequently, Flash will crash when saving a .fla file and give me this error :An unexpected failure occurred while processing a Debug Active Process API request".

I can't get anything done!

I have tried:
- reinstalling the programme in VGA mode.
- redownloading the programme.
- installing it on a different system (but similar CPU and configuration).
- installing the most recent drivers for my video card and sound cards.

And I get the same problems, over and over (and over) again.

Can anyone help me sort this out?

Is there some problem with Flash on dual processor systems?

Sorry for re-posting the message.

John Dowdell
1/26/2004 5:04:15 PM
"Phlesch", I'm assuming you picked up the old trial from a book or
similar CD. I'm also assuming that the fact that the program starts up,
and that you reinstalled, guards against subtle damage to the code itself.

Nothing from your description of the NT system jumped out at me as being
an obvious cause. You mentioned that you had done some driver testing,
but I'm not sure how far you get in the other troubleshooting steps
mentioned in this technote:
http://www.macromedia.com/go/14776

Right now there could be any number of causes for the unusual result,
but paring away those possibilities, one at a time, through such a
troubleshooting path is the fastest way I've seen to find out what the
difference is.


Alain, if you didn't get a contact back from us, then something's wrong
-- thanks for bringing it up so that we can find out what happened. I've
forwarded your message here internally so that we can get to the
bottom of it.

(For the original problem itself, I'm glad you determined that it was
just the one file which caused the problem. Some such damage can be
cured by a "File > Save As" to totally rewrite the file, but if the
damage is in a large media element like an audio clip or bitmap then
this tactic would usually not help.)

jd







--
John Dowdell, Macromedia Developer Support, San Francisco CA
Search technotes: http://www.macromedia.com/support/search/
Soapbox column: http://www.macromedia.com/desdev/jd_forum/
Daily technical diary: http://www.macromedia.com/go/blog_jd
Offlist mail is trapped by spam-filters... best here, thanks!
Tom Unger
1/26/2004 7:49:17 PM
PierreAlain;
Although your problem may well be "file specific" (rather than "system
specific"), Fwiw I remember seeing an older technote at MM's flash support
dealing with running flash on dual processor systems--should come up in a
search. -Tom Unger

PierreAlain
1/26/2004 8:13:57 PM
I had something more or less similar, with especially one .fla witch crashes
MX. I sent to MM assistance, thay asked the file, and... I never heard of
them again.

The commun point I see is Dual proc. I already saw here someone having such
problem, and he was having also a dual proc.

Note, that with new files, it hasn't crash for a mounth. The problem that I
still have to live with the risk one fla file stop to be workable.

--

Pierre Alain

pie@lifnet.com

phlesch
1/27/2004 3:02:34 AM
Thank you guys!

Look at this

http://www.macromedia.com/support/flash/ts/documents/dual_nt.htm

.. . . and I quote

"Flash crashes after a few minutes of use

Issue
After a few minutes of working in Flash on a dual processor machine running Windows NT, the program freezes or crashes.

Reason
Though Flash will run on dual processor machines, Flash was not designed to take advantage of dual processor functionality and will not run faster than single processor machines. This can occasionally cause unexpected results.

Solution
To resolve this, set the affinity for a single processor for Flash.
This will cause no loss in performance or functionality of the Flash application.

Use the steps below to set the affinity to a single processor:
1

Right after launching the program, open the Task Manager.
2

Choose the Processes tab.
3 Right-click on the Flash3.exe process and choose Set Affinity.
4 Select which CPU to use, and choose OK."


it works!

thank you!!

AddThis Social Bookmark Button