Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Could not load Scene into memory

368 views
Skip to first unread message

Gi0vanni

unread,
Jul 24, 2007, 10:09:28 PM7/24/07
to
i've been working on this fla file for about a week and tonight i get a major problem. Could not load scene into memory. you document may be damaged? i can't find any resolution on the web. any ideas

Gi0vanni

unread,
Jul 25, 2007, 6:22:37 AM7/25/07
to
what? hasn't any one seen this before?

roozbeh_fir

unread,
Jul 26, 2007, 3:45:05 AM7/26/07
to
Does your movie contains preloader? If not how did you get that scene couldn't load into? Clarify your problem so that we can be much of help.

roozbeh_fir

unread,
Jul 26, 2007, 3:45:17 AM7/26/07
to
Does your movie contain preloader? If not how did you get that scene couldn't load into? Clarify your problem so that we can be much of help.

Gi0vanni

unread,
Jul 26, 2007, 9:45:39 PM7/26/07
to
i have a xxx.fla thats i've been workingon. its a web site. the last publish
worked perfect. i save it to a jump drive. i restarted my computer and could
not open the xxx.fla file after the restart which was on my jump drive still
attached to the computer.

gindala

unread,
Sep 19, 2007, 8:49:48 PM9/19/07
to
Hi

I am really amazed that no one from Adobe has answered this?

I have had exactly the same problem tonight and I think the error appears when
a FLA file that your corrupted FLA links library items from has been deleted.

Somehow the FLA still references to the old file it was created from.

For example: you have a file called ver_1.FLA, you do some changes, save it as
ver_2.FLA. All works fine until you delete ver_1.FLA, all of a sudden you will
get error messages opening ver_2.FLA.

I am sure there must be some directory that need to be flushed to reset the
library references?

Stefan

gindala

unread,
Oct 19, 2007, 1:23:14 AM10/19/07
to
Adobe shame on you for still not resolving this issue - I am so disappointed.
How many versions of Flash has had this bug and how many devoted Adobe users
have lost hours of work without one reply from Adobe? Bad bad bad!!!

BRUSHfire

unread,
Nov 12, 2007, 8:42:11 AM11/12/07
to
This has happened to me before. I worked on a Flash site that ended up being
9.5 MB with no problems at all. I came back to it a week later with some new
images to add. After adding the new images to the library and the site, making
the file 9.6MB Flash crashed, could not export properly - "probably due to low
memory". I noticed Flash was crashing when I clicked on the newly added bitmaps
in the library and determined it was the new files that were not reading
properly. All I did was open the library and deleted all the bitmap images in
the problem folder, re-saved under a new file name and imported the bitmaps
back into the library. After I reinserted the bitmaps to their locations within
the site I saved and exported.... and it worked fine. No more crashes! Strange.

nbernardo

unread,
Jan 30, 2008, 10:55:00 AM1/30/08
to
I'm experiencing a similar problem. When I save a file under a different name I
get an alert saying that the bitmap in my library is damaged and I should
delete it. Is this a problem with image referencing? It IS VERY FRUSTRATING.
Any documentation would be greatly appreciated.


Jerry

unread,
Jan 31, 2008, 11:23:22 AM1/31/08
to

it sounds like you should delete it and then put it back

myoldid

unread,
Jun 2, 2008, 1:34:11 AM6/2/08
to
I have a similar problem, I think it might have to do with large file size, but probably something screwed up with library. It's really annoying. I just got set back a whole day's worth of work.

arm...@gmail.com

unread,
Dec 23, 2013, 4:41:05 AM12/23/13
to
I had the same problem on flash CC, document size was correct (1.7 MB) but it didn't load scene and library.

doing following steps fixed my problem:

1. close flash CC
2. change "fileName.fla" to "fileName.zip"
3. open "fileName.zip"
4. delete "PublishSetting.xml"
5. rename "fileName.zip" to "fileName.fla"
6. open fla file!

it only clears your publish setting. but fixed the problem (at least fixed mine)
0 new messages