Out of memory, then xfl corrupted

I had a very simple flash project going in CS5, when suddenly an out of memory exception appeared. I save my .xfl project - and restarted flash. Only to find that I could not reload the project...
Anybody else experienced xfl problems? Is it too soon to start using it?
A zip of the (broken) project is here:
http://test.staunsholm.dk/transit/dj%20pres.zip
Regards,
Mikkel Staunsholm

Seems I'm not the only with these problems:
http://forums.adobe.com/thread/638346?tstart=30
long story short, it sounds like saving as cs4-fla is the way to go for now. Shame, I really like the xfl-format, especially because it plays much nicer with version control systems.
Btw. I'm running CS5 on Windows 7.
Mkkl.

Similar Messages

  • Out of memory error, possibly corrupted fs?

    I just got my tour, and I love it. However I ran into a weird problem.
    The desktop manager never show the BB messager as installed, then it tries to uninstall it. If I check the checkbox it installs over it and breaks it.
    I was able to fix the messanger by reinstalling over the old one from the app store OTA.
    Now, vilingo wont run, it throws an out of memory error. I've tried removing it and reinstalling it every way I can think of.
    Also sometimes it takes 20+ minutes to reboot.
    The crux of the matter is I could easily exchange it at this point, do you think I should or should I wipe it? any other suggestions?
    Thanks,
    Chance

    No, not corrupted. You are out of memory..... just like a computer that is bogged down with too much stuff, your phone can only handle so much. The reason your apps keep disabling is most likely it is archiving them to make room for everything else you've got going. The biggest memory muncher is most likely pics or videos... as few as 5 or 6 pics and throw your phone off.  The other thing you might be noticing is missing call logs, messages, or emails.... again, the phone is automatically clearing them out of memory (possibly before you[ve even had a chance to view them) to make room for everything else you've saved to it.
    As far as startup times, again... MEMORY. the more files the blackberry has to scan through when it starts up (and it scans EVERY file EVERY time) the longer its going to take.
    The solution for all of these issues is to get a memory card and use your desktop software to transfer all of the pic video and ringtone content to it. you can transfer one the phone itesself but its a time consuming process.  after this is done pull your battery... startup still takes about 10 min on the tour but you should be ok.  The phone will automatically save media to the SD card once its installed. 

  • Out of memory error when writing large file

    I have the piece of code below which works fine for writing small files, but when it encounters much larger files (>80M), the jvm throws an out of memory error.
    I believe it has something to do with the Stream classes. If I were to replace my PrintStream reference with the System.out object (which is commented out below), then it runs fine.
    Anyone else encountered this before?
         print = new PrintStream(new FileOutputStream(new File(a_persistDir, getCacheFilename()),
                                                                false));
    //      print = System.out;
              for(Iterator strings = m_lookupTable.keySet().iterator(); strings.hasNext(); ) {
                   StringBuffer sb = new StringBuffer();
                   String string = (String) strings.next();
                   String id = string;
                   sb.append(string).append(KEY_VALUE_SEPARATOR);
                   Collection ids = (Collection) m_lookupTable.get(id);
                   for(Iterator idsIter = ids.iterator(); idsIter.hasNext();) {
                        IBlockingResult blockingResult = (IBlockingResult) idsIter.next();
                        sb.append(blockingResult.getId()).append(VALUE_SEPARATOR);
                   print.println(sb.toString());
                   print.flush();
    } catch (IOException e) {
    } finally {
         if( print != null )
              print.close();
    }

    Yes, my first code would just print the strings as I got them. But it was running out of memory then as well. I thought of constructing a StringBuffer first because I was afraid that the PrintStream wasn't allocating the memory correctly.
    I've also tried flushing the PrintStream after every line is written but I still run into trouble.

  • CS4 InDesign to PDF: Out of memory error

    I have a user that gets an interesting error when attempting to PDF a particular file from InDesign.
    I know each ID file holds a lot of settings and links to resources so it is likely that particular file that is causing the problem as other ID files PDF just fine!
    What happens it it flashes on the screen Error: Out of Memory then opens a text file in notepad with the error below.
    The PC has 4GB of memory, so I doubt its a memory problem!
    Error text file displayed:
    %%[ ProductName: Distiller ]%%
    %%[Page: 1]%%
    %%[ Error: ioerror; OffendingCommand: imageDistiller ]%%
    Stack:
    -dict-
    -mark-
    -save-
    -mark-
    -save-
    %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced
    I just suggested that she create a new ID file as I am sure that one will print fine, but it would be nice to know how to check & repair ID files in the future...  Any help tips are appreciated...

    To complex of a vector graphic or to large of a file to write out.  It's usually due to too much transparency interaction and big files.
    Try and write out a Postscript file and distill.

  • I'm getting a general error message then out of memory trying to add a new sequence

    Anyone know how to fix??  i am getting a general error message and then out of memory when adding a new squence??  Help!

    The General Error warning is usually associated with incompatible files.
    Out of Memory can be caused by corrupted clips, incompatible files and still images that use a color mode other than RGB.

  • Cannot open Sequence:  "Operation Not Allowed" then "Out of Memory"

    I quit FCS1 for about 5 hours and returned. When I opened the project I was working on I got these messages: "Operation Not Allowed" then "Out of Memory" when I attempt to open my master working sequence. Other sequences (small nests) do open within the project. The project opens, so the file is not corrupt. A back-up copy of the same project file on a separate physical disc generates the same results. I deleted the prefs and User Data folder, even ran FCP Rescue. Same results. Then I resorted to the Autosave Vault. The two most recent saves resulted in the same error messages. Fortunately the next did not. I lost a considerable amount of work. The system says my memory is OK (6GB). Any ideas? (An attempt to open on a FCS2 machine {8GB RAM} resulted in the same two error messages.)
    The project is fairly lengthy (90 mins) and does have numerous 1 and 2 frame audio edits. Nothing particularly unusual in the video tracks--although I am mixing DV and HDV. It doesn't seem to me these attributes would matter, just throwing them out there.

    ...removing and re-rendering is a great idea, if you've got the time.
    And if during render you get the same out of memory error, try rendering "in-to-out", rendering small chunks until you get to a chunk which brings up the error. Then, you've found an offending "corrupt" file.

  • HT201317 dear, i have a question please.  if i want to keep a folder of pictures in my icloud account; then delete this folder off my phone would it be deleted from icloud account too?? cause im running out of memory on my iphone

    dear, i have a question please.  if i want to keep a folder of pictures in my icloud account; then delete this folder off my phone would it be deleted from icloud account too?? cause im running out of memory on my iphone
    thanks

    You can't use icloud to store photos.  There's a service called photo stream which is used to sync photos from one device to another, but this can't be used to store photos permanently.
    Always sync photos from a device to your computer,  Then you can delete them from the device.
    Read this...  import photos to your computer...
    http://support.apple.com/kb/HT4083

  • Error message: 'Codec not found. You may be using a compression type without the corresponding hardware card' - then - 'Error. Out of memory'

    Hi all. This is a new error I've never seen before.
    It's stopping me doing anything at all really.
    As soon as I start up FCP and click on a sequence I get this message: 'Codec not found. You may be using a compression type without the corresponding hardware card.'
    Then I click on OK and it says 'Error - Out of memory.'
    I've heard rumours that it could be the fact I'm using a strange type of JPEG, but it still happens with PNGs.
    I've made sure my scratch disks are all going to the right place. I also have 100gb of free space.
    The version of FCP I'm using is 6.0.5. I'm using an iMac with OSX 10.4.11 (yes, I know it's old!) and I've downloaded the latest version of Quicktime.
    Help, anyone? I have an assignment due in tomorrow.
    Many thanks...

    p.s. having looked at other posts, perhaps I am missing some (or all) of the relevant codecs?
    In the folder Macintosh HD > Library > Quicktime
    there is basically nothing. Do you think this is the problem?
    If so, where do I download FCP codecs from?
    Many thanks..

  • Adobe Illustrator "out of memory" when saving then crashes

    We have a user who uses Illustrator.  Every once and a while she will have the issue where it says that it is out of Memory (RAM).  I checked and at that time she had over 4Gb of physical memory left and the Swap was at 0 of 8.6Gb.  Am I reading the memory wrong or is something else the issue?  Also the CPU was at 5% used and the hard drive has almost 600Gb free.  She is using a USB 3.0 external hdd to open and save to.  When it crashes the below error is given.

    It doesn't happen every time and it is different files.  I can't get the user to only keep stuff on the computer.  Do you think that is the issue?  It used to work fine for months then now it just started doing this on a pretty regular basis, but I can't find anything that I can do to make it repeatable.

  • Receiving "Not Found" - then "Error:Out of Memory" trying to open Sequence

    I have received a FCP Project edited in 2009 from the UK and have pulled the project file onto my workstation and all of the media onto an ext HD. I have also reconnected all of the media. However, when I try and open one of the Sequences in the project - I receive the following error "Not Found" then once I click off of that a second error "Error:Out of Memory". All of the other sequence in the project open fine.
    Initially, I was able to open the original project file and open the sequence - but when I tried to copy the sequence & paste into a new project-I would receive the errors. Now I am receiving the same errors in the original project.
    At first I thought it might be an problem with the computer but I have tried this on two different work stations /computers so I don't think it would be a prefs ( trash preferences) issue. Also footage was first on an XRAID and then I brought it to an external HD, so I don't think it had anything to do with permission issues.
    This sequence is critical that I am able to get to it as it is part of a TV episode, so I would very much appreciate any help / advice on fixing this problem ASAP!
    Thanks!

    p.s. having looked at other posts, perhaps I am missing some (or all) of the relevant codecs?
    In the folder Macintosh HD > Library > Quicktime
    there is basically nothing. Do you think this is the problem?
    If so, where do I download FCP codecs from?
    Many thanks..

  • I have a new iPad air using autocad 360, when I go to open a file it gets around 70% done and then states I am out of memory.

    I am trying to open autocad files on my new iPad air 64mb, I have loaded autocad 360, every time in open the file I get a message that I'm out of memory can some one help

    Quit all other open apps then reset the iPad and try again.
    Double click the Home button to show the screen with running and recently used apps. Each app icon will have a sample page above it. Flick up on the page (not the app icon) and the page will fly away and the app icon will disappear. This quits that app. Then reset your device. Press and hold the Home and Sleep buttons simultaneously until the Apple logo appears. Let go of the buttons and let the device restart.
    If that doesn't help I would delete the app and download a fresh copy. Be sure you save the file somewhere other than in the app when you do this.

  • InDesign 2.0.2 & Out of Memory

    I just want to state first I have searched everywhere and for every phrase I can think of, and while I have found a couple hits as to the cause, nothing has fixed this issue...
    Background:
    I work for a rather large media company who owns a mixture of online and print publications. We have been using InDesign 2.0.2 since it's release, and I have been one of the main persons responsible for it's usage in our workflow for the past 4 years. There have been a number of informal discussions, and even a formal discussion or two, about migrating the templates we use to InDesign CS3 which we also have licenses and installs for. However, that migration project keeps getting pushed aside for more important projects. So please keep in mind that upgrading, for us, is not an option in order to resolve this issue at this time.
    A Quick Overview of What We Do:
    There are two main products that we offer our child companies - One product for the companies themselves to list vehicles for their clients (in this product their clients are car dealerships), and another product for a private party (e.g., Joe Blow internet user) to list their cars for sell. Both applications run a fairly similar process in that they hand off data gathered from the websites to a custom built application. That application can be considered a parent application, and it then distributes work to its children processes which run on several different servers. Four of those servers run our InDesign processes.
    Two of our InDesign machines are physical dedicated servers with a quad core CPU, and 2GB of RAM with 2GB swap. The other two InDesign machines are runnning as VMWare virtual machines with 2 CPU cores and 2GB of RAM with 2GB swap. All four machines are Windows Server 2003, and all files (artwork, XML files) in which these machines use to build the final output file are remotely connected via a file server.
    In the past we've seen the issue I am about to describe on our virtual machines only, and on only one machine at a time. Each time we have corrected the issue by simply re-deploying that virtual machine and the InDesign application. However, now it's spread over to our physical boxes too, and currently happening on all four machines at this point in time.
    The Problem and What We Have Tried:
    As stated earlier, we run a parent/child setup on various servers where the parent hands off work to it's children processes whom are connected in a client/server model via a TCP connection. These children perform a single function - to process data dumped from the websites ultimately into an XML format readable by InDesign. There are other steps and XML outputs, but this is the only one that matters for this discussion.
    This child then reports back to the parent that it has completed its work, and the parent will pass that work off to one of our InDesign servers. The child will then automatically launch InDesign, and InDesign will open the files it needs in order to populate various elements in the INDT file. This consists of EPS/PDF/JPEG images for Headers, Footers, Vehicle Images, etc. and also populates certain strings in the document to those read from the XML document to automate the population of the data. Basically we feed it some image files, an INDT, and an XML, and it gives us back a pretty PDF.
    The problem that we're seeing is that upon opening some of our INDT files on these machines, InDesign will immediately pop up an error dialog stating that it's out of memory. Obviously, when looking at Task Manager we can see that memory is not an issue. InDesign will be using around 70mb of RAM, and the system will show 1.7GB free physical RAM.
    Another problem is that it will go weeks, months, even maybe a year before happening again after re-building the machine its happening on. We have never been able to locate a root cause as to why this keeps happening. However, we have narrowed down that changes to the servers are not occurring at the time these issues start so we have ruled out configuration changes, system patches, etc.
    One of the issues with the virtual machines that has seemed to have caused this, and was believed to be the issue until recently, was that the paging file would become corrupt. Thus rebuilding the VM was the only way to resolve. However, we have checked and double checked and the paging files on these servers are currently ok.
    Obviously with such an old version of InDesign you can imagine that searching Google is quite difficult. Google likes to think we're asking about CS2, however, there have been a couple hits on 2.0.2.
    These hits include information such as possible font corruption and deleting saved settings/defaults files. We have downloaded and used Microsoft's font validator on the fonts, and each have passed. We have also tried deleting the saved settings and defaults files numerious times, as well as deleting the font cache files so that InDesign will re-create them.
    The paging files were also re-sized, turned off, moved to another local disk, etc. without any impact.
    As this is the first time we've seen this impact multiple machines at the same time, and especially since its happening on both physical machines and virtual machines, we are trying to think of things which are common to these 4 servers. However, the only thing they really share are the mounted network shares. To get around this we've also tried opening our INDT's locally after copying them off the network, but the issue remains the same.
    Another thing I've read is that the INDT itself may be corrupted, and to simply re-save the file. As I have a copy of InDesign locally to build these INDT's, this is also something I've tried but with no luck. The files don't seem to be corrupted. The same file which causes InDesign to crash on these four servers load perfectly fine on my local machine.
    As we have escalated this to other key people here, our last suggestion was to either re-build the machines or contact Adobe for support. However, InDesign 2.0.2 is no longer a supported product due to its age so I am here - asking you, the community, for any assistance you can provide short of re-deploying these machines.
    We would appreciate any assistance you can provide, and thank you for reading this.

    Peter,
    Thank you for the reply. In regards to...
    "First, are you running InDesign Server, or trying to use a standalone ID
    install as a server which is totally unsupported and probably not
    allowed under the EULA? Nor is Windows Server a supported OS for
    non-server versions of ID, so you're pretty much on your own as far as
    what will work and what won't."
    InDesign is setup, and launched, like any normal application on any other OS. We have a special user setup which runs the client process of our client/server model in the foreground, and it is that client process that then launches InDesign. This user is always logged in as a result.
    "If, in fact, your templates are corrupt, in version 2.0.2 you're SOL as
    far as being able to clean them up. Rebuild from scratch. The .inx
    format was not introduced until version 3, and were you working in CS3
    you could try Remove minor corruption by exporting but there would still be no guarantee of success."
    This was one of the things I was trying to remember as I was typing. The .inx export, then re-saving as an .indt. However, as I build these templates locally, I have tried opening the file and re-saving it under a different file name. I then upload that new file and re-name back to the original name, although again, with no luck. I figure if the template is indeed corrupted that it's possible I'm just re-saving those issues even to a new file.
    Re-Building from scratch is possible, however, this has happened with brand new templates as well. Again, this issue when it appears seems completely random. It chooses both new and old files alike, and those files appear to be just fine. It's just this time, for some reason, all four machines are doing it which has never happened before. Right now there are probably a few hundred templates which currently throw this error immediately upon loading (and all of the ones I've tried on my local desktop work just fine), and around the same amount that are exhibiting odd behavior with their output.
    "Now on to the problem and solutions. You've already rejected the best
    idea, which is to upgrade. The out of memory error might be file
    corruption, or it might be realted to the use of .eps files which are
    notorious for that sort of error. Reasaving in native formats is the
    usual solution."
    This is actually something I hadn't thought of or tried. I will re-save the EPS files as PDF's and give it ago with one, however, there are a couple things with that as well. One is that the Out of Memory error pops up on these machines as soon as I open the blank template. There are no graphics imported by default. So really it's just a plain document of whatever size, with a few boxes and text labels. Also, because we work in print and the fact these two applications have been used for so long, most of the artwork our child companies have provided us over the years are in this EPS format. There are a few thousand of them, and converting them all will take more time than it's worth for my company. They would not approve of my dedicating time to do that. New artwork we receive has been mostly in PDF as of late which does help in that regard, however.

  • Out of memory with no swap causes disk activity

    Can someone explain what exactly is being read/written from/to disk in this situation?
    I have 2 GB of RAM and no swap partitions. Occasionally I'll forget how inefficient gwenview is at displaying very large images and accidentally double-click one. The entire system freezes; even alt+sysrq keystrokes are ineffective (and yes I do have them enabled).
    For about 5 minutes, the system is locked up and the hard drive light is flickering. That scares me a bit, because with no swap, what could it possibly be doing for 5 straight minutes? I used to think it was synching before doing the OOM-killing, but there's no way a sync could take that long. Judging from the sound of the hard drive, it's hda (the drive / and all the other system partitions are on).
    A few times after recovering from this I've run extensive data verification and never found any evidence of corruption, but I'd like to know for sure that the kernel isn't randomly deciding to use some filesystem as swap space.
    In the mean time, I'm playing with disabling overcommit -- setting vm.overcommit_memory = 2 in /etc/sysctl.conf. That enforces a hard memory commit limit of swap size + overcommit_ratio * ram size (so I've read) -- and I've also read that the default overcommit_ratio is only 50%. What the bloody hell? It's almost like someone thinks swap is more important than RAM -- hell-llo, I have 2 GB of RAM so that I can get *away* from swap!
    Anyway, I've set the ratio to 97% and so far things seem happy -- if I deliberately run out of memory, the process that did it always gets killed instantly and the system doesn't freeze up on OOM anymore."
    Another thing -- in all my out of memory situations so far, VMWare has been running. I suppose it's possible that VMWare is the one doing the swappage; I'll have to investigate that further.
    ~Felix.

    I think I've finally figured this out. It's a kernel bug -- I'm guessing that under normal circumstances, the "cached" column in the free command "doesn't count" towards how much memory the system thinks it's using. After all, it's just cached copies of stuff that should be elsewhere, and if you run out of memory, you can safely dump that, right? Unfortunately, /dev/shm is counted under cached rather than used memory (as I discovered in an earlier post).
    So if I've got 500 MB of stuff in /dev/shm * (which is where I mount my /tmp), there's now 500MB of stuff in the "cached" column that really does count -- system reaches all RAM full, decides it needs to dump cache, and suddenly finds that the 500MB it thought it could use isn't usable. For some reason it takes about 5 minutes of hard drive thrashing (probably because it's already chucked all of the system libraries, etc. out of cached and needs to re-read them from disk every time) before something finally figures out that it really is out of memory and that that 500MB isn't letting go and invokes OOM-killer.
    *: VMWare does this; it creates a 512MB file (the amount of RAM in my virtual machine) then hides it by keeping the file open and deleting it, so the inode's still there, but you can't see it and it makes the df command really perplexing... but that's another story.
    I haven't had a chance to try this with a newer kernel (maybe they've fixed it now?); I'm still running 2.6.23-ARCH here. (pacman -Syu upgrades are a major production for me because I have lots of RAID arrays and things, and an nvidia graphics card, and I use gnucash which sometimes needs manual recompiling, and so on...)

  • Excel 2011 version 14.4.8 running on an iMac gets "out of memory" messages.

    HELP!!!   Excel 2011 running on an iMac with OS 10.10.2 and 16GB Ram gets "out of memory" messages.  When I monitor processes with "Activity Monitor", I am using less than half of my RAM.  The Excel workbook has many sheets and also some macros.  The basic workbook has been running for about two and half years starting in August 2012 without any problems until I upgraded to Yosemite in early December 2014.  Now I often have to restore the entire file content because it gets corrupted after not being able to save the file because of the "out of memory" message.  I can take a file and its content that ran fine a year ago and run it today and it will eventually get corrupted and get the "Out of memory" message after saving/quitting/re-opening the file any where from 6 to 15 to 25 times.  I think I need to have more memory allocated to Excel, but Yosemite doesn't provide any way for the user to interact with the memory management process.  I have also experienced the very same problem on my MacBook Pro that runs Yosemite.  I have worked file/path name length issues, closely inspected the macros that normally don't run except when activated with a user pressed button, and made sure I don't have any weird links within the workbook or even links to another file outside the workbook.  This problem seems to get worse as a continue to fill up the spread sheet with more financial data.  This Excel workbook is used to manage my club's finances; I am the club treasurer.  I have searched the internet for clues about similar problems and have found none!
    My iMac is a 27-inch, Late 2009 with a 2.8GHz Intel Core i7 Processor.  It includes 16GB of 1067 MHz DDR3 RAM.  The hard drive is a fussed 1TB rotating HD with 128 GB SSD.  This hardware has been running for about 27 months.  I am a very advanced Mac user that programs Excel and Filemaker and repairs Macs for others.

      I am a very advanced Mac user that programs Excel and Filemaker and repairs Macs for others.
    I am a not a very advanced Mac user that uses programs like Excel and Filemaker and avoids any repairs of Macs for others
    Given the caveat, have you tried reinstall of Office? Your MS Office 2011 may have become corrupted.  After upgrading to Yosemite I had to reinstall my Office 2011.  No crashes.
    The current version of Office 2011 is 14.4.8.
    First - find your Office 2011 install disc with the product key # - and only then remove Office according to MS instructions
    http://support.microsoft.com/kb/2398768
    Or go here to DianefromOregon's site for help removing Office 2011:
    http://www.officeformachelp.com/2012/12/office-for-mac-2011-remove-office/
    Then Reinstall from DVD
    Then enter your Product #
    After successfully reinstalling Office 2011,  update your Office product using the Software update within Office called Microsoft Update or going to the Help menu within Word or Excel or PowerPoint and select Update.
    It may take a few times before you get to final upgrade to current Office version.
    It should be 14.4.8 as of current date.
    How to locate product keys
    http://support.microsoft.com/kb/2279109
    or here on locating product keys
    http://office.about.com/od/MicrosoftOfficeMac/a/Best-3-Ways-To-Find-Microsoft-Of fice-For-Mac-Key-Codes.htm
    Note is updated as of March 4, 2015

  • "out of memory" box again and again

    When i'm adding clips to a sequence, a separate box'll come up that says "out of memory". I have about 293 GB left in storage according to what the hard drive info says so I don't know what the problem is. I can get it to work again after hitting save a few times but it still happens again after a few minutes. Why is this happening and how do I stop it?

    Well, no, David, that's not the only (nor even the main) reason this happens.
    For instance, I have 4 gig of Apple-approved RAM, and I'm getting this message.
    A lot of times what it is is a corrupt file playing havoc with the math (dividing by zero will ALWAYS run you out of memory before the poor processor can figger out the answer!).
    In many cases, one can determine where the corrupt file is by marking a short segment and "rendering in to out". Start with one half of your sequence...if it renders, then the problem is in the second half...if you get the stupid error message, then keep rendering short parts of the first half until you come to the part that triggers the message...and there, you'll find the corrupt file.
    Now this won't solve the problem every time, but it's worked for me (in fact, I'm here now because I'm gettting the message, and solving it). Try it.

Maybe you are looking for