Fireworks CS5 crashes often due to buggy memory handling. Will there be a patch?

Question

Fireworks CS5 has a major bug that causes a memory leak or memory "cap" where the application stops functioning once it has used approximately 1.5 GB of memory or so. (I read that 2GB was the cap, but I have never seen Fireworks make it to 2GB).  I only have 10 undos set in Fireworks, so I know that's not the problem. I have searched high and low to resolve this, but it seems like Adobe just hasn't recognized this as a high priority.
I read other discussions about the same problem and I now believe that Adobe either doesn't read the forums or they don't care. I hope this is not the case because I truly love the product. But, for the record, I shouldn't have to:
- "Limit the number of undos to less than 100" (I have limited mine to 10, but after 6 months of trial and error I have found that to be irrelevant. The errors occur anyway). Don't encumber your users with such an archaic request. This is like a software bug from 1985.
- "Save, shut down, and restart Fireworks every hour or so". Are you kidding? I can't believe someone on the forums even suggested this. This isn't a solution to the Fireworks bug. This is a work around that does nothing to prevent the error from occuring. Sometimes the error occurs on the very first click after opening a file in Fireworks, after a full system restart. A 5MB file takes 3 minutes to open in Fireworks on my quad-core 3Ghz machine with 8GB of memory. I don't mind that, but I shouldn't have to do it every 30 to 60 minutes. Users shouldn't have to look for "workarounds" to keep a software application running without crashing, especially such an expensive application. I think Fireworks is worth every penny, but only if it runs without crashing.
Perhaps most importantly, I cannot - ever - open two 5MB files in Fireworks at one time. Which makes it extremely cumbersome to impossible to copy/paste content between two files. In fact, I am designing a web application in Fireworks, and I've had to split the app into approximately 15 different files because Fireworks can't handle files bigger than 6 or 7MB.
I had the same problem with CS4 on a different machine, so I know it's not a new issue.  I have Fireworks installed on two PCs, both have quad core 3Ghz processors, one PC has 6GB of RAM, the other has 8GB. Once an hour I have to shut down what I'm working on and wait several minutes for Fireworks to reopen the file.  Sometimes Fireworks just stops responding and won't let me save my work at all. And since there is no autosave in Fireworks, I probably lose work at least once a day.
Please, please, please address this... I love Fireworks, and I'd really like to keep using it.

Answer 1

I am using Fireworks CS5 in Windows 7 to sketch a large site, and it was taking an extremely long time to do anything and seemed to crash on me once or twice every hour. I saved every couple of minutes and could at least rely on my last save being able to be reloaded. However, a few days ago, I lost a lot of work when Fireworks crashed halfway through the save and destroyed the file. At the time, my most recent backup copy that I had on another drive was a day old, so that crash was not only frustrating but hazardous to my project deadlines (needless to say, I've since implemented a more aggressive backup policy). Anyway, I searched for answers and forums about the problem, and I'm disappointed that it seems that it's a common problem for a lot of folks that has been around for a very long time throughout multiple releases of the software. Memory and resources also seem to be a common factor in contributing to the crashes and are also a theme in the few solution responses that I was able to find. I hope that Adobe will respond with a once-and-for-all fix / a much more efficient and stable way for Fireworks to do its magic. I typically have had very positive things to say about Adobe software and was even the one who recommended the suite for my work, but especially as "well seasoned" and *expensive* as the software is, there is no excuse for any major, well-tested component of it by now to be crashing so consistenly and causing so many problems for so many people.
The solution to the crashing that seems to work for me so far - and I hope that it works for you as well: I doubled the size of my swap/paging file to ~4GB and set the maximum to double that (~8GB). Since I did that, Fireworks has only crashed once (only once.. as if that is even acceptable considering the short time since then). It still runs fairly slowly (granted, I'm working on a large project, so I can tolerate that more), but at least I can use it again.
Hope that helps! Best,
-j