Skip navigation
Currently Being Moderated

Fireworks CS6 - Still the same memory issues and crashes.

May 11, 2012 4:00 AM

I had hoped that the inability to save even the simplest documents due to a range of errors from "Unable to complete your request. An error occured", to "Not enough memory", to "Error Code 80000001) would be fixed.

 

Adobe is completely ignoring their best design solution for mobile application design, now over 5 years!

 

I am working on a document that has 12 42x42 icons and nothing else, still I cannot save my document half of the time. The tool is unusable as is. It is highly unstable and endangers work, not to speak about the frustration it causes me.

 

My Fireworks hardly uses more than 300MB of memory, still hitting ctrl+s almost always results in an error. It is impossible to work longer than 30 minutes without needing to restart the tool.

 

 

My version is CS6 with the Creatve Cloud.

 

My computer is an i7 Win 7 x64 PC with 16GB of ram and a SSD disk configuration. My system is not the issue.

 

 

I am highly dissapointed by Adobe once again.

 
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    May 11, 2012 8:28 AM   in reply to Andrej Balaz

    Wow, this is so odd. I'm using CS6 and am experiencing NOTHING like this. In fact (in 32-bit), the experience has improved in terms of speed and reliability. I wonder exactly what configurations by Adobe lead to such terrible results in x64?

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 1:32 PM   in reply to Andrej Balaz

    Yep - styles, pages, symbols and all. It's really messed up that adobe hasn't given Fireworks the proper attention. Have you tried any sort of emulator, compatibiliity modes, etc.?

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 4:34 PM   in reply to Andrej Balaz

    You may want to look at this - at the very least, you can get a better idea of what's causing the problem. http://stackoverflow.com/questions/192876/set-windows-process-or-user- memory-limit/1289945#1289945

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 6:10 PM   in reply to Andrej Balaz

    Andrej Balaz wrote:

     

    I have read somewhere, that Fireworks can access only the FIRST 2-3GB of system memory. Since I have such a large amount of system memory and almost always running several adobe applications at once, I am wondering if that could be the issue. However, only an Adobe developer could help with that.

    Yes, that is exactly the problem.  Because Fireworks is a 32bit application, it is only the first 2 to 3 GB that Fireworks can access.  And of course there are likely other apps running trying to take some of that initial 2-3 GBs of RAM as well.  It doesn't matter how much RAM you have in total. 

     

    The other reason for your problem is the way Windows handle memory management.  OS X on the Mac handles memory a lot better so even if you have a lot of RAM used up by other apps already, once you open up Fireworks the OS does a good job of freeing up the necessary memory it needs.  Windows doesn't seem to handle this as well.

     
    |
    Mark as:
  • Currently Being Moderated
    May 12, 2012 3:08 AM   in reply to Andrej Balaz

    i can't understand why adobe treats its only wireframing and screendesign application this bad. the error in your screenshot exists now more than five years, and none of the two guys of the fireworks programming team seems to care. they probably only work the last week before a new release to update the splasscreen and icons.

     

    most of the innovation of the last 3 releases did come from third party extensions developers and user suggestions. that's fine but at least adobe should take care of the bugs.

     

    well, irony can help to overcome all this.

     
    |
    Mark as:
  • Currently Being Moderated
    May 12, 2012 5:14 AM   in reply to niduma

    Since these products cost hundreds or thousands of dollars/euros/pounds, this is something that is unacceptable. If I had a Mac, I would be using Sketch, that's true, but are there any good alternatives to this Adobe BS on Windows? I can only think of Expression Studio, which is pretty solid.

     
    |
    Mark as:
  • Currently Being Moderated
    May 12, 2012 5:17 AM   in reply to Andrej Balaz

    I've been using Fireworks since Macromedia's first beta. I love(d) Fireworks until Adobe started butchering and neglecting it.  But for some reason I have continued using Fireworks despite its numerous flaws and neglect by Adobe. CS6 is the final straw for me. 

     

    It has clear to me that Adobe is not going to allocate the resources necessary to clean up Fireworks. Not now, not ever. We're pretty much at the point where the Fireworks needs a rewrite anyway as it has become a bloated mess of half-complete marketing features, sort of like Photoshop. (At least Photoshop is 64-bit though.)

     

    Although I won't be able to replace Photoshop and InDesign anytime in the near future, I am having spectacular results with some Fireworks alternatives.  Bohemian Software's Sketch 2.0 and Pixelmator 2.01 are going places. I do not think that either is quite ready to replace Fireworks on my system yet, but they are almost there. For the most part though, I am using Sketch 2.0 for a good 80% of the work I typically do in Fireworks. The speed and responsiveness of these two programs alone is unbelievable at first when you come from a Fireworks background. The developers of said programs are also very active in communicating with their users.

     

    I suggest that all of you, who are able, should start investigating your own alternatives to Fireworks. You are creative professionals and shouldn't have to deal with wonky software getting in the way of your creativity, your workflow.

     

    I wish you all the best.

     
    |
    Mark as:
  • Currently Being Moderated
    May 12, 2012 5:18 AM   in reply to Aloof

    On the Windows side I would concur, Espression Studio is surprisingly solid.

     
    |
    Mark as:
  • Currently Being Moderated
    May 12, 2012 1:50 PM   in reply to lazypixelmachine

    @lazypixelmachine thanks for the sketch tip. i looked at it when 1.o came out and found it not quite ready. i will test it again and report back how it did. besides that i completely agree with you. as you said, we are creative professionals but adobe is doing a terribly amateurish job. that's what frustrates me the most.

     
    |
    Mark as:
  • Currently Being Moderated
    May 13, 2012 1:47 AM   in reply to lazypixelmachine

    @lazypixelmachine It is a really liberating reading your posts, they voice my feelings to the pinpoint.

     

    Been a long Fireworks fan, also since early Macromedia stages. I as well can't replace Adobe (Fireworks, Illustrator, Photoshop) entirely, but I realize it is going to a painful workflow transition sooner than later. In order to deliver high quality to clients, I am in need of a working software that mirrors professional. It is sure nice that the frustration that has been built up since around CS3 is not just me being a baby about things.

     

    CS6 is also the final straw for me. So thanks again for heads up. I rather spend some hours changing my workflow than continue paying and hope for a change (I have been since at least around 2007).

     
    |
    Mark as:
  • Currently Being Moderated
    May 16, 2012 9:15 PM   in reply to Daryl Barnes

    This SHOULD be the case. But FW documents "run out of memory" at 300mb - 700mb. Actually 700 mb is usually the max we can use before we get the dreaded errors.

     

    I have 24Gb of RAM!!! I SHOULD be able to access at the minimum 2gb given it's a 32-bit app. But that just isn't the case.

     

    Something fundamental about FW needs to change.

     

    I have had to build an Extension that fakes the functionality of Pages and States and saves them as seperate documents so that we can avoid this drama at work. NOT ACCEPTABLE ADOBE!!!

     

    I have built a plugin that helps track memory performance of Fireworks... saves us about 80% of the time when it comes to crashes. I might see if work will allow me to make it public.

     
    |
    Mark as:
  • Currently Being Moderated
    May 17, 2012 3:12 PM   in reply to Andrej Balaz

    Ive been working with FW today, about 10 hours continously, it crashes three times and had problems to save two times. Im using two different files to save to, aftr having a corrupt file due to a saving crash. I dont know whether this is good or bad. Its annoying, but I could live with it. BUT what really makes me angry are these little sloppy bugs all over the app. Circles look somehow weird, the dropshadow cant be used, color management causes headache. I need some sort of workaround for almost every little working step.

     

    Not to mention the slowness and delays in my workflow, i. e. when opening the preview window to check out a hover or when waiting for the inspector to react.

     

    I guess, they where just not ready programming, when Adobe launched CS6. Im quit sure, all the issues will be fixed till summer with the next update. They are working on it :)

     
    |
    Mark as:
  • Currently Being Moderated
    May 18, 2012 1:55 AM   in reply to graugans Design

    don't put any hope in it that those bugs will be corrected this summer. all those exists since many years and nobody at the fireworks team seems to care about it. the workflow of fireworks would great and fast if the interface response could keep up with the speed of the user.

     

    i really doubt that the fireworks team is working on anything between new releases. i know it is provocative to say that but it seems like that after every new release. if you look at the list of changes for cs6 it is quite apparent that most of them are small tweaks to improve the workflow but only one handles performance issues and only few actually correct drawing issues. and even the mentioned perforformance improvements sound like a workaround for somthing that is completely wrong at the core of fireworks.

     

    http://helpx.adobe.com/fireworks/using/whats-new-cs6.html

     
    |
    Mark as:
  • Currently Being Moderated
    May 18, 2012 1:56 AM   in reply to niduma

    We must put all our problems on the wishlist of Fireworks and then post continously at the Fireworks Facebook page, as this is red by a lot of people and Adobe has to react somehow. There are also a few well known professionals out there, like Jim Babbage for example, wonder what they say to that issue?

     
    |
    Mark as:
  • Currently Being Moderated
    May 22, 2012 9:15 AM   in reply to graugans Design

    I honestly do not run into the glut of problems people seem to experience. I get the "occasional" hang, but Word crashes on me more often than FW.

     

    Once in a while, FW tells me it can't save a file because it's in use elsewhere (and it's not in use elsewhere). In those situations, a resave works.

     

    I am in the habit (not because of Fireworks) of saving files often, so I might be avoiding some of the issues mentioned here.

     

    I'm on a MacBook Pro, using Snow Leopard - have not upgraded to Lion yet.

     

    It can be hard to track down issues, too. For example, I know one user who has three identical Windows systems, yet only one of those systems is plagued with problems when using Fireworks.

     

    The dev team for Fireworks is a dedicated - but small - team. They genuinely want to produce a solid product and do their best to address issues - legacy and new - in each release. They can't get to all of them in one go, unfortunately.

     

    You can help by reporting issues WITH details to the Adobe wishlist. The wish list IS read by Adobe (unlike this user-to-user forum) and is almost like a form of triage. The more common a problem is (highly reported), and the better documented those problems are, the more likely they are to bubble up to the top where they can be worked on by the dev team.

     

    Here's the URL:

     

    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

     

    HTH

     
    |
    Mark as:
  • Currently Being Moderated
    May 22, 2012 10:22 AM   in reply to Jim_Babbage

    Excellent! Thanks Jim - for the link and informative, dedicated comment. Also I think this is an issue isolated to PC 64bit.

     
    |
    Mark as:
  • Currently Being Moderated
    May 22, 2012 11:36 AM   in reply to motionman95

    I have a fairly nice Dell with a 2.93Ghz dual core, 4GB RAM and an Nvidia GeForce 9300 on Win7SP1...not going to knock your socks off but runs any other graphics program just fine. Now, even when I use CS6 on my Lenovo D10, dual 3.0G XEON Quad Core with 16GB RAM and a 768mb FX4600 card on Win7SP1 64bit and get the same thing, well there's a problem.

     
    |
    Mark as:
  • Currently Being Moderated
    May 22, 2012 10:46 PM   in reply to Jim_Babbage

    It seems as if the performance-issue is the biggest problem of Fw. Many users here in the forum as well as out there i. e. at Facebook complain about lack of stability in any case. Might it be crashes or out-of-memory-issues, slow response of the UI or simply bad rendered forms and effects, the overall impression of FW is a bit bad-tasty.

    I think that the dev team should have made maximum effort to fix the biggest bugs for CS6, and I cant believe that they didnt know about. Of course, there are always bugs, even in word ;), but when reading the complaints, most of Fw problems seem to exist for years now. It feels so sloppy. So sit down and do your homework and make this programm working properly.

     

    People in this forum are not any amateurs or trolls who love to complain about software. We are professionalls, we all paid for FW, working with the programm everyday and we all want it to work properly and without causing headache

     

    @Jim_Babbage: I have a 10MB(!!!) FW png and it takes 8 to 12 seconds to save and about 25sec(!!!!) to render a preview. This is ridiulous. And if the dev team cant handle all the problems it has to be increased. We are not talking any garage company, do we?

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 3:15 AM   in reply to graugans Design

    @ All , If you are seeing memory issue or any other instablility issues.Please add a bug in the wish list as suggested by Jim babbage.Also please share your files if possible and Submit the crash reports using Adobe Crash reporter.Your files and crash logs will help us investigate the issue.

     

    Thanks

    Adobe Fireworks team

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 3:32 AM   in reply to Shubhashri CG

    How does this work? Cant find the Crash Reporter. Only Crash Report is send to Apple.

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 4:35 AM   in reply to graugans Design

    Few minutes after the Apple crash report appears, Adobe Crash reporter will also appear.If you don't get the Crash reporter.Please copy the contents in "Problem Details and System Configuration" that appears in Apple crash report.Save the content and share it with us.

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 4:59 AM   in reply to Shubhashri CG

    Ok. Where will I send it to?

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 5:12 AM   in reply to graugans Design

    Please add a bug in wishlist  https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform  then we will approach you for the files/Crash log.

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 9:33 PM   in reply to Andrej Balaz

    Adobe Crash Reporter is Mac only. For Windows, when the crash happens Windows Error Reporting dialog is expected to pop up.

    Request you to submit the crash via that also.

     

    Mac or Win, Adobe has access to all the crash reports only if the user opts to submit them.

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 1:51 AM   in reply to Jim_Babbage

    @Jim_Babbage: "Once in a while, FW tells me it can't save a file because it's in use elsewhere (and it's not in use elsewhere). In those situations, a resave works." - This might actually be because another system resource is hogging it. It happens to me if I have included an attachment in Apple Mail for instance. Closing mail, will free the file. It is prolly due to Apple restrictions than Adobe.

     

    Anyway, just to confirm what people say and what @CItzwerth said. I have three main computers (1 office, 1 home, 1 on the go). They are all blazing fast modern stuff. A Mac Pro with 8 cores and 32Gb mem, a i7-3930k 6 core and a Macbook Air 11' (late 2011) with an i7/4GB mem. They all suck at using Fireworks, sometimes grinds down to a halt (e.g. more than 100small objects is impossible unless they are bitmap).

     

    I use FW mainly for complex UI sketches, all of it being vector and the reason why I use FW over AI is because FW is the de facto tool for UI work, no doubt.

     

    The basic is, I should not have to strive with mem problems and slow UI. My computers can handle it, the software should enable me to have the best workflow I can have.

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 3:25 AM   in reply to Sarthak Singhal

    @Sarthak Singhal:

     

    I have several crash logs right now. Where to send them to? The wishform only allows 2000 characters max.

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 4:32 AM   in reply to graugans Design

    @Citzwerth,

     

    Have sent you a mail.Please send the crash logs there.

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 6:31 AM   in reply to Andrej Balaz

    Gang, we've heard from two separate engineers in less than 48 hours. Let's cut them some slack. They are people just like us. They are doing their best with the resources allotted to them. Like it or not, Fireworks is not Photoshop and the resources the FW team has are not at the same level a huge program like Photoshop would have.

     

    Thank you to those who've already posted their info to the wish form. The detail used here in many cases is exactly the kind of thing (along with sample files) that they need.

     

    Can I ask, those of you who a having difficulties, how many of you are using the Master page, and if you are using it, do you have interactive elements on the Master Page?

     

    I had a situation a while back where I had button symbols OS master page, and the file took forev to load. As soon as I moved those web objects to one of the child pages, and shared the layer, the loading process improved significantly. My situation might be uniques, but I thought I'd share.

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 1:16 AM   in reply to Jim_Babbage

    @Jim_Babbage, indeed, when deleting/removing/disabling the master page and using shared layers instead, the preview seems to load much faster, although theres some strange stuff going on, whole layers are not shown at all, buttons are invincible although mouse changes to pointer and so on. Have to examine further, might be my fault, but, yes, masterpage seems to play a big role in slowing down. Thanks for the hint!

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 10:37 AM   in reply to graugans Design

    Some clarification on the Master page issue I experienced:

     

    I had a Master page with 6 duplicate states. Each state (my bad, as I was in a rush) included a set of button symbols, when only one state (state 1) really needed them.

     

    It looks like this duplication is what caused a lot of my issues. When I removed the button symbols from the other states, performance and load time improved greatly.

     

    HTH

     
    |
    Mark as:
1 2 3 Previous Next
Actions

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