Forums

This topic is locked

OUT OF MEMORY with MX 2004 only

Posted 09 Nov 2003 16:09:00
1
has voted
09 Nov 2003 16:09:00 mike hamlett posted:
running 2 pc's.
xp pro 512 memory
win 98 2nd ed. 512 memory
both getting intermal errors/out of memory when launching fireworks mx 2004 with dreamweaver loaded. the xp pc before installling mx 2004 could run both these programs with all the normal virus protection/ie/outlook with no problems. before mx 2004 i was running mx on my 98 pc. i could have dreamweaver/fireworks/norton antivirus/and ie running. now with mx 2004 i cannot. i have had my 98 pc reformated and operating system and drivers resinstalled/all software reinstalled/loaded 512mb ram/installed mcafee instead of norton. if i boot the machine and shut down all nonessentials such as activesync/virus protecton, i can get dreamweaver/fireworks to coexist but dont open your browser or the system will crash. i was going to xp pro on my home pc until my office pc starting choking on mx 2004 also. i love mx 2004. it is laid out great, easy to use and i am more productive with it. but because it is such a resource hog, it may have to be thrown out with the trash.

any help would be appreciated. this is not a basic pc problem that can be fixed by saying just shut down all non essentials or upgrade your operating system. apparently mx 2004, design assumes it is the only app running on the pc and wants everything. this problem was not an issue before 2004, so some major architecture changes had to occur. i am not the only one with this problem. i see alot of memory issues with mx 2004 posted but have not heard of a fix or patch being posted to help.

Replies

Replied 11 Nov 2003 23:00:29
11 Nov 2003 23:00:29 Scott Fegette replied:
Hey, M-
Honestly, I'd open a ticket directly with tech support on this to better track/look into it- difficult to diagnose these types of problems via message boards.

Disabling 'realtime' virus scans *only on the MX/MX2004 application directories themselves* may be another option if you haven't tried it already- this alone can solve a lot of related problems (especially since you noted things worked better without it). DW specifically has a LOT of its functionality in separate JS/HTML files in the Configuration directory- when virus scanners are particularly aggressive they can definitely help DW peg the processor during startup and certain functions, as they block the app from reading the file right away while the 'realtime' scan is performed on each individual config file.

You can contact tech support directly here (2 free incidents w/the purchase), honestly it's the best way to dive deep with memory errors/issues:
www.macromedia.com/support/email/complimentary/main.cgi

Hope this helps!


- Scott

scott fegette
macromedia, inc.

Reply to this topic