Skip to main content
A
Andrej Balaz
Known Participant
May 11, 2012
Question

Fireworks CS6 - Still the same memory issues and crashes.

  • May 11, 2012
  • 13 replies
  • 46958 views

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.

    This topic has been closed for replies.

    13 replies

    Show previous replies
    L
    lazypixelmachine
    Participant
    May 12, 2012

    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.

      N
      niduma
      Participant
      May 12, 2012

      @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.

      A
      Andrej BalazAuthor
      Known Participant
      May 11, 2012

      I have attached an image. Memory is not the issue here. There is something deeply wrong with the SAVING in Fireworks since CS3.

      M
      motionman95
      Participating Frequently
      May 11, 2012

      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.?

      A
      Andrej BalazAuthor
      Known Participant
      May 11, 2012

      So far I have only tried to delete the whole preferences file of Fireworks. Problem persists. I really don't know why.

      M
      motionman95
      Participating Frequently
      May 11, 2012

      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?

        A
        Andrej BalazAuthor
        Known Participant
        May 11, 2012

        Are you using styles, symbols, pages and states? I think that once you start using any of those, the document pretty much breaks at some point. I cannot save more than half of the times. Nothing helps, nor restarting the app, nor setting processor affinity to one core, nor reinstalling. I am running FW CS5 and CS6 as parallel installations. In fact instead of getting an error message like usual in CS5, the CS6 sometimes simply just crashes on save.

          A
          Andrej BalazAuthor
          Known Participant
          May 11, 2012

          By the way, FW is still a 32 bit app. They have just increased some caps for 64 bit systems, nothing revolutionary happened. I wonder why Fireworks is not in focus for Adobe. Photoshop is too desorganized for proper application design and lacking vectors, whereas Illustrator is simply too slow when texturing vectors or creating states.

            Terms & ConditionsAccessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices