I have several Flash Professional projects (primarily AIR Android), that fail to open in Flash Professional CC with the following error message:
Could not load scene into memory. Your document may be damaged.
These same FLA files open fine in Flash Professional CS6, so I know that they are not damaged.
Any thoughts on how to resolve this?
UPDATE: I was able to recreate one of the files in Flash CC by creating a new project in CC and migrating the library, publish settings, etc. So the failure seems to be in properly reading the FLA created in CS6.
Can you go through this document and see if it helps your case?
Unfortunately, seems worse than I expected. Following the instructions in the link about did not resolve the issue.
As I mentioned previously, I had a work around of creating a new AIR Android project in CC, copy/pasting the library and manually updating the project settings, etc.
After closing Flash Professional CC, reopening and opening the project created in CC, I get the same error message:
Could not load scene into memory. Your document may be damaged.
This project worked fine prior to closing FP CC and was created entirely in CC. At this point, I'll have to switch back to CS6 until a resolution can be found. I can't recreate the project everytime I close Flash. The only "unusual thing" about this project is an ANE file.
Again, this would appear to be an issue reading certain project files (both CS6 and CC).
UPDATE: The problem seems to relate to having SWC or ANE files specified in the ActionScript Settings of the document (FLA).
It doesn't appear to happen with every SWC or ANE, but I have been able to replicate with a SWC version of the GreenSock animation library and a custom ANE I created. I can create a project, add them in the ActionScript settings and access them in my code. The project will compile and run as expected. However, if I close Flash, when I come back in and open the FLA, it is unable to load as described above.
Do you get the error, if you remove the greensock.swc from the library path and use the "com" folder instead;
Will it be possible to share the sample project which is causing the issue?
Adobe Flash Professional Team
I will try the com folder route... This will likely work, but wouldn't work for an ANE.
I can certainly put together a sample project - I have been able to replicate consistently just by creating a new project and including the swc/ane.
How can I get the sample project to you?
Please change the java memory settings
"Xmx256m" to "Xmx512m"
Java memory file
C:\Users\<user name>\AppData\Local\Adobe\Flash CC\en_US\Configuration\ActionScript 3.0
Value to update: -Xmx512m
Then open the file , let me know if its work for you.
Thanks for the suggestion...
I had tried something similar previously - updated the -Xmx value in the jvm.ini file located under Program Files/Adobe/Adobe Flash CC/Common/First Run/ActionScript 3.0.
However, changing this value in either place doesn't correct the issue. I will upload a sample file as soon as I get a chance to pull one together.
Thanks everyone for your assistance in this matter...
I believe that I have determined the cause of this issue. One of my primary development folders has an ampersand in the directory path. So when adding the greensock lib or ANE, the path included an ampersand (&) in the path. This didn't cause problems in CS6, but in CC it appears to.
I was able to track this down by opening the FLA as a zip and examining the PublishSettings.xml file within. I noticed that the library entries in this file containing ampersands where not escaped (&), which could be throwing off the xml parsing during the open process.
For the FLA file in question, I was able to edit PublishSettings.xml to either 1) remove the library entries with the & or 2) modify to a different path. Adding the modified PublishSettings.xml back into the FLA (zip), the project would then open properly in Flash CC.
So from this exercise, it would appear the ampersand in a path is now a problem in Flash CC - at least in library paths.
I'm having the same problem, a little different scenario though. The FLA is originally from Flash CS6, saved as a Flash CC FLA.
After saving and reopening it defaulted to "Scene 2" and wrote to the output panel, "Could not load scene into memory. Your document may be damaged." The library was empty and nothing was on the stage. File properties (stage width/height, framerate, etc) were correct, there was just nothing in the library.
Try #1: I retrieved the original FLA from GitHub and tried it again. This time it was okay after a save and reopen. All good. Later I saved again, closed, and reopen the next day. It was corrupted again.
Try #2: I retrieved the original FLA from GitHub and tried it again. This time I copied all the library items from the old library to a fresh, new Flash CC FLA. Saved, closed, and reopened. Corrupted file again.
Try #3: I retrieved the original FLA again. This time I copied the library items to a fresh XFL file. Saved, closed, everything okay. Later saved, closed, found the file corrupted again. Digging into the ~/Library folder of the XFL package there's nothing that seems wrong... all the XML files are there.
Try #4: Opened on a different computer. Still corrupted.
As long as I have the FLA/XFL open it won't go corrupt. Its the moment I save and close that there are problems. I'm working on a Mac OS 10.8, I uninstalled and reinstalled both Flash CS6/CC and Flash Builder 4.7 to ensure it wasn't bad installs. Library is a mix of buttons, bitmaps, and movieClips. Flash CS6 now suffers the same fate too after the latest update.
The symptons are very similar to mine... I tried a number of similar iterations, but in my case I could always open it in CS6 (Windows x64) - even if it was reported corrupt by CC. I also created a new CC project and copied the lib items, project settings, etc. only to have the file reported as corrupt after saving and reopen. The lack of library items, etc. is also what I am seeing.
I'm still testing to ensure that my issue is resolved, but it looks like the "Could not load scene into memory. Your document may be damaged." error relates to the reading of the supporting XML files in the FLA/XFL structure. For my case, the library paths had an & in them, but when saved out the text was not properly escaped - resulting in invalid XML in the PublishSettings.xml. Oddly, CS6 seemed to be able to ignore this problem (reading the & correctly even though not escaped). I even went so far as to edit the PublishSettings.xml file in the FLA and add the escaping on the & - the file opened fine. Of course, once I make a change and save it in CC, the escaped ampersand is lost and the file is corrupt again.
I'll continue to provide updates as I work through my testing - especially if I find more information. Something has obviously changed in the reading and writing of the support XML files in the FLA/XFL formats.
Very helpful jg716, thanks. Figured out that I could indeed open in Flash CS6 this morning. I took that corrupt XFL and opened in Flash CS6 (which opened!), a quick edit, save, close Flash CS6, open the XFL in Flash CC... bingo! Could reopen on Flash CC again. So it definitely seems like its Flash CC and the way it saves to the disk. While Flash CC is open... no problem. But the moment you close the Flash CC file and try to reopen its done.
This is exactly my issue. I seem to be able to work all day in a file when I have created it from scratch and build, even for hours. But when I save, quit and reopen, the file is beyond recovery: no symbols in the library at all, nothing on the stage.
I had this exact same problem. Saving successfully, reloading, editing, saving, until one day it stopped loading with the same "Could not load scene into memory. Your document may be damaged." However, I didn't have & in any of my paths.
I cracked open the .fla (renamed to .zip), exacted to a folder layout like .xfl, and compared the directories to a new, small xfl-saved Flash CC project.
There were obvious differences in the files, but I found the "corrupted" .fla had a PublishSettings.xml in the root folder that was over 300k in size, while the newly saved .xfl was only 7k. The corrupted file had the same "Default" publish profile XML repeated a number of times with no apparent differences. After deleting all of the duplicate entries and saving out the reduced PublishSettings.xml, the project finally loaded in Flash CC.
I am having the same issue. Albeit, sometimes I won't get the memory error but the file will open and my Library will be completely empty and it will not use my document class no matter what. I have had to recreate a flash file 4 times in 3 days now and this is totally ridiculous. I have not had any success with the suggestions others have made.
Same issue guys - I was working perfectly this morning, first time in CC and using FB4.7 as the code editor. Finished what was needed, close and came back and BLANK project with that corrupt message. I was using the greensock swc in there otherwise nothing hectic. Tried to change jvn as mentioned above with no success. What a let down . How do you get the publishsettings.xml file to check for the ampersands?