In my case it happened when saving to a local hard disk. I copied a

bunch of library symbols from a CS4 FLA into a CS5 FLA, tried to save >

crash > could not load CS5 FLA anymore. The FLA:s were in different folders.

No problems since saving every project as XFL instead of FLA.

19.10.2010 14:16, nbshark123 kirjoitti:

I have the feeling it's a saving to a network problem.

   

If you're reading this and have this problem, are you saving to a network drive? If so, does the problem still occur when saving to a regular hard disk?

Well, I think even though recent advancement in HTML and JS technologies gave quite robust tools for web development, these tools can not completely replace Flash. I'm not a fan of 'Flash vs. JS (or HTML5)' talks. I believe these two technologies have their own purpose and are not always interchangeable: for web applications - yes, for rich media presentations - hardly HTML/JS can replace Flash. ... but this talk is not for this topic.

After these troubles I've switched to saving as CS4 format (happily current project allows me to use CS4 format). But this is very inconvenient as I always have to us 'Save as' command and going through two prompting dialogs. %(  For CS5 project I would probably try saving in uncompressed CS5 format... until Adobe actually release some patch to fix this problem.

Nivesh,

I have automatic updates turned on and I install all updates it warns me on. Anyway, I've downloaded this update, but as the instalation completed within seconds after launch I think I've already had it installed - and Flash still crashes on saving CS5 format.

Besides there is other very unplesant bug - to avoid crashing currently I save my sources in CS4 format which is very inconvenient because of need to use Save as dialog, but which at least avoids Flash crashing. But I noticed that sometimes when I test project or simply publish SWF, Flash marks source file as saved (removes * from the file name in the tab) and also manages file as if it is saved, but it is not saved. So one time when I finished my work and simply closed the file expecting Flash to ask me for save I didn't get the dialog and the program simply closed the file with all my work I've done during that session lost!

I like new CS5 package, but due to such very very inconvenient bugs it becomes a very unpleasing experience using it, and as I see from this and many similar posts - not only for me.

I hope some patch that really fixes all these bugs would be released soon, as this is very important issue.

Best,

Art.

I've just spent another hour on unsaved work when Flash CS5 crashed again...

Each day 1-2 hours of my time goes on dealing with Flash crashes. Thats my final project with CS5 and I'm switching back to CS4 as it becomes damn nuts workin with this @$@%!

I've been wondering about this too, not just Flash, but most of my CS5 suite, and also a few others apps that aren't Adobe related.

I'd heard that support for XP was being dropped by M$, but having read a bit about that I see its only XP SP2, not SP3, and they plan to continue supporting XPSP3 until 2015, new computers being offered the ability to downgrade from W7, simply because so many businesses aren't ready/can't afford to upgrade. So I really hope support / testing for apps made by Adobe, for XPSP3 isn't slackening... and here I was about to say "Well, it is a 10 year old OS".

I'm using Windows 7 32bit and Flash crashes often! And I saw here complaints from people using MacOS and Win7 64bit So I can tell thats hardly an OS issue.

Clearly this issue hasn't been solved by Adobe yet. I have installed all the updates, and Flash CS5 still crashes when i save, and corrupts the file. Maybe Adobe doesn't care at all anymore.

This question is NOT answered.  Still experiencing Crashes and Corrupt files.

Win7 x64 - Flash 11.0.2.489 - I've been using CS5 for 2 days and had 5 crashes, and two corrupt files. This is unacceptable.

How about they post recovery steps, since saving as a .zip gives access to all your files.

How could this project get shipped with this issue? I'm dumbfounded.

The issue is with the DOMDocoument.xml file inside the zip.  It's being corrupted on save.  The rest of the pieces are in tact inside the zip.  What I would love is a way to transfer my LIBRARY assets into another .fla without a corrupt DOMDocument.xml file.

Anyone have a process for this?

If you have a compiled flash (swf), then you could try a decompiler, worked for me here. I know its not the smartest choice, but it did the job.

I have posted RECOVERY STEPS for library items here: http://stackoverflow.com/questions/4453743/flash-cs5-crash-corrupted-f iles-how-can-i-get-my-xml-library-assets-back-into-a/4453942#4453942

This does not recover your timeline, but it will give you back your LIBRARY items.  Hope this helps someone at least salvage something.

That is incredible! Did someone tested Flash CS5 before releasing at all!!?? Or they simply opened that, saw that everuthing looks fine and started shipping? After reading about such problems it seems very like that!

lol same here, they will most likely never fix it...

Hi Adobe/Nivesh/whoever is monitoring this post,

This issue is still not resolved.  I have a brand new Mac Pro workstation and every time I try to save a Flash file, it takes 5 minutes to save.  It always freezes at a certain point in the save process and finder displays Flash as "not responding" in the Force Quit window.  This is not normal behavior for any version of Flash up until now or any other software you make, for that matter.  I give you credit that it does save and does not corrupt the file, but based on user feedback you've received, you should be aware that this is a bug in the software and we need to know that you're planning on addressing it.

If Flash cannot be relied upon, it cannot be used, and if your userbase rejects it, you can bet it will be bad for business.  It is also troubling that you have marked this post as "answered" when the consensus is that the problem still exists.

Please confirm you are working on a fix for this issue and, if possible, provide an ETA.

Thanks,
Patrick

No problem, glad to make you smile =)

While it may be a completely unconnected issue and I may be complaining in the wrong place, my assumption is that it's associated because CS4 saved the same files much more quickly, on a slower Macbook Pro no less.  I've upgraded to CS5 with a brand new Mac Pro workstation and everything in CS5 runs like a dream--except Flash when I save.  I should clock it, it may be more like 3 minutes, but it's a long save, and the program doesn't respond during the save.  I'm not saving to a network, this is my personal machine and I'm saving directly to my HDD.  FLA is not corrupt because it saves fine.  It does have some complex objects, vector brush drawings, but nothing that took so long in CS4 on a slower machine.

I think Flash's saving engine is just buggy, and I'm fortunate with a really fast machine.  I assume if I force quit Flash during the save that it would certainly corrupt my file, considering it's mid-save.

Not trying to complain about everything, but there is a definite issue and Adobe hasn't said or done anything to address it yet.

- Patrick

This bug has resulted in my creative studio (6 offices in 3 countries) completely skipping CS5. We work on centralized network server for our asset creation and this bug makes CS5 unstable and unusable for us.

Way more than sour grapes here. Our IT department has officially reported the bug and the only thing worse that Flash CS5 is Adobe support!

It really does seem like the CS5 file structure change is in 'beta' and CS5 is the public beta and you probably shouldn't be charging for beta quality product.

I'm knocking on the largest piece of wood we have in the office just as I say this, but the latest patches seem to have removed any further trouble for me, on WinXPSP3.

Having said that, I think VeryVito has said something very sensible. Its definately a trend and Adobe are making it easier to justify moving away from a platform that is expensive and now unreliable upon release, at least for some of us. I too have reported the bug, and got a response, I sent files et al - and heard no further, one can only assume the issue is being worked on - and I'm not confident at all that just because I haven't seen the bug(s) when I've had to open an FLA and edit (read: not dare to start a new file), that it won't return to haunt me.

@Armitage-Art - 3 minutes or 5 minutes, it doesn't matter eh? I am an avid saver, because saving has always stood me in good stead. if I look up from my pc, I save, if I copy a large chunk of code, I save. If I don't remember saving in the last few minutes, I save... those 3-5 minutes would stack up rather quickly and annoyingly if I were experiencing the bug you have been!

ps. I had so many woes with installing CS5 when CS3 was still installed, that I had to remove them both, and start from scratch. Then, in dismay I tried to uninstall CS5 and get CS3 back on board - but then the same serial issues cropped up - and thank goodness I was able to re-install CS5. So I'm stuck with that package until my manager allows me to waste further non-chargeable hours formatting my machine and putting CS3 back on.

oh they want money for 5.5? they know alot of their customers will not accept this?

same here!

flash crash when saving.

so glad its not only me.

also, it sometimes duplicated symbols and scenes before it crashes, did anyone here experience that?

if the scenes window is open you can clearly see that the scenes "magicly" all duplicates, and after that it crashes all together...

hours of work gone to waste...