Skip navigation
BrownChiLD03
Currently Being Moderated

Fireworks CS5 = OUT OF MEMORY problem

Jul 8, 2010 2:30 AM

Hi Guys

 


I've been getting this "out of memory" problem when working on fireworks. Not really that often but when it does occur it's annoying i have to close my open documents in FW and reopen it..

 

When this error occurs, the elements in FW are not shown anymore i just get this boxes that say "not enough memory"

 

Now I'd probably suspect my PC running out of RAM or something, if it wasnt for the fact that I have 8GB DDR2 1100Mhz Ram installed on my Windows 7 x64 Machine.. and I have plenty of swap disk left too.. and the fact that when this happened i'm only consumung 5GB of my 8GB tank..

 

So could this be a FW memory handling problem?

 

Regards

 
Replies
  • Currently Being Moderated
    Jul 8, 2010 7:32 PM   in reply to BrownChiLD03

    Please delete the Adobe Fireworks cookies and Application Data

     

    Just Delete the  Fireworks file in C:\Documents and Settings\Administrator\Application Data.

     

    Hopes that help you.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 9, 2010 8:21 AM   in reply to BrownChiLD03

    Same problem with 12GB of RAM - same platform - Windows 7 doesn't have that pathname to clear the cookies?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 11, 2010 4:26 AM   in reply to BrownChiLD03

    For Fireworks, it doesn't matter how much RAM you have installed -- it handles memory in a very specific manner, and cannot use more than ~ 2 GB of RAM. Once this memory is exausted for it, Fw will become instable.

     

    My suggestions -- to avoid this kind of problem:

     

    1) Reduce number of UNDO steps to approx. 100. (this can be set in Preferences)

     

    2) When working with large files and/or with many files, periodically restart Fireworks (after a few hours of extensive work), wait until Fireworks.exe disappears from running processes, then start it again.

     

    Working in this manner will probably make this error never appear...

     

    Hope this helps!

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 12, 2010 10:51 AM   in reply to Michel Bozgounov

    I get the same problem and my undo steps are set to 20.  Just a ****** product with a ****** development team.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 14, 2010 8:16 AM   in reply to BrownChiLD03

    Hi,

     

    I've got the same problem too and it doesn't matter how many undo-steps I've configured. Closing other Fireworks documents and other running programs gives you 2 or 3 more edit steps until the error message appears again. According to Task-Manager Fireworks only uses not more than 400 MB of my 3,24 GB memory (Win XP SP3)

     

    My Document:

    10 Pages, 10 to 20 Styles, 15 Layers (mostly shared), ca. 205 objects with groups (ungrouped ca. 500)

    Every 2 hours Fireworks needs a restart.

     

    It seems to be a very very strongheaded bug, because it's reported from users since CS3 (afaIk). But I'm very thankful. In CS5 at least I can save my work after the error message appears.

     

    I don't give up hope, that someday this bug (and many others) will be fixed.

     

    @Adobe: Is a bugfixing-update on schedule (in the near future)?

     

    Regards

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 20, 2010 7:36 AM   in reply to BrownChiLD03

    The same problem here with FW CS5 from Master Collection. Windows 7, 64bit, 8GB RAM, i5.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 5, 2010 9:39 AM   in reply to mandrzej

    The actual problem is with GDI objects not RAM. CS5 doesn't do a good job of cleaning them up when you close documents. Closing Fireworks every few hours will correct the problem because app is removed from memory but this shouldn't be needed. The dev team should be able to clear these objects when a document is closed so we don't have to restart the app so often. IMHO

     

    If you want to view how many GDI objects are being used by any Windows application,

    open Task Manager

    select View from the tool bar

    choose Select Columns

    check the box next to GDI Objects

    Click OK.

     

    Jason

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 8, 2010 4:40 AM   in reply to Jason MacKinnon

    thanks Jason very helpful

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 8, 2010 5:00 AM   in reply to Jason MacKinnon

    yes 7,000 of the things (GDI objects) in CS5 compared to 998 in CS3 doing

    the same task

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 9:47 AM   in reply to BrownChiLD03

    from my experience fireworks cs5 crashes when it reach a limit of 1.4 gb of ram used

     

    that is very little because many of the nowadays web projects is made by many pages and many objects images, vectorial

     

    this program need to be 64 bit for serious users, who need to work with lots of multipage files

     

    c'mon adobe just optimize this for  users who have plenty of ram and lots of work

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 12, 2011 2:06 AM   in reply to BrownChiLD03

    Adobe is full of BS when it comes to the support of their products. This problem persists since years and nobody seems to care. Fireworks is thus an unusable product for any of the tasks it is claimed to have been developed for: multi-state prototyping, massive webdesign with the use of symbols, vector and bitmap cooperation.

     

    I have a 16GB memory pool, this application however cannot cope with it, that's why I assemble my designs in Illustrator. (which is not suitable at all. It is not supporting states, it's slicing and pixel precision are very bad and unreliable)

     

    But memory rules it all and crashes are not acceptable. I just wonder why we pay the thousands it costs for it.

     
    |
    Mark as:
  • Takashi Morifusa
    87 posts
    Nov 12, 2008
    Currently Being Moderated
    Oct 31, 2011 11:06 AM   in reply to Aloof

    Unfortunately Adobe Fireworks CS5 is 32bit application and can access to maximum 2GB. That's 32bits application limitation. Thus, whether you have 8GB, 24GB RAM loaded, Fireworks phisically access to 2GB is the max. We are investigating this to improve memory access for the future version of Fireworks.

     

    Thanks,

    Takashi

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 1, 2011 11:04 AM   in reply to Takashi Morifusa

    Er how long do we have to wait for this 64bit version? I'm suprised it needs investigation because its been done for Photoshop already so do what they did. But I'm guessing the code is poorly architected due to its long legacy and that it makes a lot of built in assumptions on 32bit architecture so any port will be long and painful and expensive to manage.

     

    CS3 didn't really need more than 2GB of memory because it was coded properly. CS5 is a massive memory leaking mess that creates way too many GDI objects and then exhausts its limited 32bit heap. The course is clear

     

    • fix the ridiculous memory leaks in CS5
    • port it to 64bit architecture

     

    I'm guessing we see neither in CS6. I'm also guessing most fireworks users would trade pointless new features for a stable and reliable tool with the existing feature set - what say you users?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 26, 2011 7:50 PM   in reply to DoktorKanukie

    Guys,

     

    As far as I know, Fw Team works hard to fix all memory issues! (And I hope to see better stability and increased max. memory limits in the next version of Fireworks.)

     

    However, Fw Team may need your help.

     

    Please, once you hit "NOT ENOUGH MEMORY" issue, submit a bug report here:

    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=1 4

     

    Include all helpful details (hardware configuration, Win version, Fw version, Fw preferences, etc.), attach Fw PNG files, and steps to reproduce (if possible),

     

    This will greatly help the team address these issues!

     

    Thanks in advance!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 6:42 AM   in reply to BrownChiLD03

    I am having the same issues, and always have since I've installed CS5.  It's nice to know that I'm not alone.  My question is, exactly how do I save the file that I've been working on all day without losing what I've done (cross my fingers).  Please tell me exactly what files to delete, and thier path.  I am running windows 7, 64 bit, with 8gb ram, i7 processor.

     

    Thanks so much.

     

    Lisa

    P.S.  It would be nice to fix this issue as Fireworks is a great program.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 3:17 AM   in reply to BrownChiLD03

    I have to agree with people here and it is worrisome to me that the first post was in 2010 and two years later, we experience the same issues.

    Fireworks in the lifeblood of my professional work, I run a agency that utilizes Fireworks primarily doing UI,UX,IXD for all sorts of projects, from medium size business to high-ends.

     

    Fireworks is the only application by Adobe and on the market that delivers the ability to work wireframes, vectorized, with pixel perfect interfaces, interaction work and full design compositions. Photoshop/Illustrator is inferior to FW when it comes to this and Adobe has to realise both the market and the advantage that they have with this. It becomes more critical as we move into new standards on the web and with apps.

     

    I am quite frustrated that it requires no more than 100 objects in a sketch/file, a few pages, layers and a file of 2mb to turn FW into a slug. This is regardless of it being run on a Win7 i7 with 8gb of ram, an i7 Macook Air with 4gb or a Mac Pro Xeon 8 core with 32gb ram.

     

    Moving objects, selecting objects, copy/paste and all sorts of minor adjustments are sluggish, respons jerky. It takes a restart once in a while, but it slugs down fast. A lot of the stuff is vector, from icons, to simple lines and objects (and no, Illustrator can't deliver what I need).

     

    I'd rather see that Adobe fixes the memory/stability issues, than introducing new features. An example: While it might be useful for someone, drop everything from texture packs (nobody uses a Berber texture fill) to anything that competes with Photoshop/Illustrator where e.g. Photoshop does better (I am thinking touching up images etc).

     

    What a lot of the users (based on fellow FW fans) would want, is a stable, responsive, well implemented software. We produce quality software for our customers and would like to see the same done for us (Adobe MC is expensive in Norway and I do not mind, but I want quality in return).

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 4:04 AM   in reply to mzetlitz

    Ok, this is what I am talking about.

     

    I have an larger size sketch for wireframes. Most of the stuff is vector, so it can be scaled up/down nicely.

    Just doing a simple thing like rasterizing them, would eat up all the memory. I rasterezied all the vector but one icon (due to the memory issue).

     

    Screen Shot 2012-03-14 at 11.53.14 AM.png

     

    So the issue is:

     

    • I can rasterize (until a memory issue) in order for the file to be workable. Instead of 2mb+ I get it under 1mb.
    • Working on a rasterized version defats the purpose, vector should work
    • A simple thing like making a raster fast surfaces the memory leak

     

    Again, been living with this for years and in many projects. Growing tired of it.

     

    Screen Shot 2012-03-14 at 11.53.38 AM.pngScreen Shot 2012-03-14 at 11.53.46 AM.png

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 26, 2012 6:37 PM   in reply to BrownChiLD03

    This is extremely annoying. Is Adobe listening? People are paying big bucks here to get their product and yet they got this. When I searched Adobe's KB, the suggestion was (laugh if you wish) max out your RAM and get a faster computer, Duh?

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 26, 2012 11:29 PM   in reply to focusbox11

    @Focusbox11,

     

    I think they are listening, but what is somewhat annoying is that fixes are included in a whole new product release, not backwards patched.

    64Bit is the only feature in FW CS6 that I see as positive. People who design for the web, needs to know CSS. CSS/jQuery theme exports produces automated markup, hardly the most helpful feature. @font-face support etc, would have been so much more welcome.

     

    While I do not mind paying high for working software, I am appalled that one has to live with a problem for so long. Some of the issues with FW has been present since CS3.

    All kudos to Macromedia who once upon a time created these products, but they were not exactly know for producing stable products and their codebase (I know from LearningSpace 5, old Macromedia product) wasn't the best. I fear that lots of old code has been present all along, which explains a lot.

     

    Adobe: With 64Bit support in FW CS6, I would like to know if this is a major rewrite of the core.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 12:23 AM   in reply to mzetlitz

    Fireworks CS6 is not 64bit app. There are many improvements in it: on Windows 7 64 bit, Fireworks will be able to use more RAM, and GDI objects issues has been fixed; but Fireworks remains 32bit app, nevertheless...

     

    The reason why Fw CS5, for example, cannot receive a new patch, is that there were made some serious updates to the core, and simply updating older Fw version(s) would be too problematic...

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 12:33 AM   in reply to Michel Bozgounov

    Thanks Michel, for the clearification.

     

    My oh my, are you sure? Then why does Adobe have a clear "64 Bit" image on the feature list for Fireworks CS6?

    By being able to run 32bit in a 64bit environment? That sounds outright lame.

     

    GDI fix is very welcome of course.

     

    So basically, the new features (until hopefully more are revealed) are:

    * Bundling the mobile packs for CS5 with CS6

    * Quicker access to colours

    * Crossing fingers for serious community love

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 12:50 AM   in reply to mzetlitz

    Older versions of Fireworks use up to 2 GB of RAM on Win 32bit/64bit; CS6 will be able to use up to 3 GB (on 64bit Win).

     

    List of new features is much longer -- I hope a detailed article (maybe on Smashing Mag?) may one day clear things up a bit!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 1:13 AM   in reply to Michel Bozgounov

    I can't but help feeling that improving it to use only 3GB is a major lagging step.

    If true, I am sure there is a reason, but it hardly does not compute.

     

    Of course, I am not a developer, so up to 3GB might mean 3GB recycled.

     

    Looking forward to that list. The community is dying to know what happens to Fireworks. Adobe should no doubt show it a lot more love.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 1:44 AM   in reply to mzetlitz

    mzetlitz wrote:

     

    Looking forward to that list. The community is dying to know what happens to Fireworks. Adobe should no doubt show it a lot more love.

    A lot more love to Fireworks would be nice! However, I am not sure this will happen anytime soon...

     

    Illustrator and Photoshop continue to copy Fireworks features:

    http://blogs.adobe.com/jnack/2012/04/generating-css-from-shapes-in-fir eworks.html

     

    ...while development resources are quite limited for Fw...

     

    Still, I like the fact that version CS6 is quite improved, and has a few nice new features. (Yep, that list should be published soon! The community definitely needs it.)

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 2:14 AM   in reply to Michel Bozgounov

    ...while development resources are quite limited for Fw...

     

    This is important. The developers working on Fireworks are no doubt doing their best and we know that their team is overshadowed by the flagship products.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 2:21 AM   in reply to mzetlitz

    mzetlitz wrote:

     

    ...while development resources are quite limited for Fw...

     

    This is important. The developers working on Fireworks are no doubt doing their best and we know that their team is overshadowed by the flagship products.

    Yes, they do their best for sure! Just look at Photoshop splash screen (Help > About...) and then at Fireworks screen... Then compare number of engineers and designers on both teams...

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2012 2:52 AM   in reply to Michel Bozgounov

    I think Adobe are seriously lacking with a vision for Fireworks - it is without doubt the best screen design tool for mobile/web and the best mobile asset production workflow tool also.

     

    I look at my colleagues struggling with their byzantine photophop layer and seperate smart objects in illustrator and wonder why on earth Adobe don't they see that Fireworks is the future for a mobile design tool. I am a serious advocate for Fireworks but this sort of behaviour undermines the message, it is the best tool for the job. Because when it falls over people say I'm going back to Photoshop.

     

    I also feel seriously on the edge and marginalised working on Windows in Fireworks when everyone else is working on Photoshop on Mac.

     

    As for the memory issues I use CS3 now although I have a CS5 licence because CS3 will stay up all day without running out of memory. I just use CS5 to import the files for things like PDF output or to transfer files from Photoshop & Illustrator (though never with 100% fidelity) . 3GB will be better and to be honest a Fireworks file is a fraction of the size of a Photoshop bloatware file so we don't need ad much memory as that.

     

    As for integrating the Fireworks best bits into Photoshop and Illustrator they are just adding more baggage to already bloated products and it will be hard to use the neat streamlines Fireworks features amongst all the historical dross freatures.

     

    Features that should be integrated in the Fireworks core are things like sub-pixel nudging - relying on John Dunning to enhance the core product is lame. I could go on ...

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points