Dreamweaver - Dreamweaver MX 2004 Trial Crashes Consistently

Author

Dreamweaver MX 2004 Trial Crashes Consistently

subgenius webforumsuser@macromedia.com

2003-11-27, 6:42 pm

I downloaded Dreamweaver MX 2004 [TRIAL VERSION] last night, and have a few serious performance issues that I can reproduce over and over again. [On WinXP home, 952 Celeron, 256mb sdram], I open a new document and then close it via the document buttons, a
nd I get a system error message telling me that DW has to close, then a memory error appears: "the instruction at '0x77f7e22a' referenced memory at '0x00000028'. Memory could not be read. Then, when I do the same thing after re-starting the app, I create
a new document, but this time close it via the "file>close" menu, I get a "While executing DWMenu_File_close command in menus.xml, the following Javascript error occurred: "exception throw in native function".

What I did to narrow things down was turn off all other applications, including especially my Avast Antivirus, and then trying it again. Same result: initiate DWMX 2004, Go to 'File>New' choose 'new html document, add a line or two of test text, try to cl
ose either via document buttons, or file menu, and either one of the above corresponding errors comes up, crashing this application.
I really want to figure this out, as it is a barrier to using/purchasing an application that I would otherwise buy without hesitation.

many, many thanks in advance

Murray *TMM*

2003-11-27, 6:42 pm

If you can reproduce these errors every time with every file, then post the
details of how to do it here. I am not able to reproduce your symptoms with
the steps below.

Diagnosing such problems is very hard without complete information about
your computer and its operating environment. Can you please tell me -

1. What is your OS?
2. What is your AntiVirus?
3. Is your AntiVirus doing realtime protection?
4. What is your Firewall?
5. What other background programs are running?
6. What extensions do you have installed?
7. Are you *running* DMX from a network shared drive?
8. Where are your 'local' files? Are they on a network shared drive?
9. Have you ever been able to run DMX or is this a recent failure?
10. Does this only seem to happen with certain files/sites?
11. Does recreating the site cache (SITE | Recreate Site Cache) help?
12. Are you using *any* OS-improving utilities like "TweakUI" for example?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.DreamweaverFAQ.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"subgenius" <webforumsuser@macromedia.com> wrote in message
news:bpus5i$3f1$1@forums.macromedia.com...

quote:

> I downloaded Dreamweaver MX 2004 [TRIAL VERSION] last night, and have a

few serious performance issues that I can reproduce over and over again. [On
WinXP home, 952 Celeron, 256mb sdram], I open a new document and then close
it via the document buttons, and I get a system error message telling me
that DW has to close, then a memory error appears: "the instruction at
'0x77f7e22a' referenced memory at '0x00000028'. Memory could not be read.
Then, when I do the same thing after re-starting the app, I create a new
document, but this time close it via the "file>close" menu, I get a "While
executing DWMenu_File_close command in menus.xml, the following Javascript
error occurred: "exception throw in native function".

quote:

>
> What I did to narrow things down was turn off all other applications,

including especially my Avast Antivirus, and then trying it again. Same
result: initiate DWMX 2004, Go to 'File>New' choose 'new html document, add
a line or two of test text, try to close either via document buttons, or
file menu, and either one of the above corresponding errors comes up,
crashing this application.

quote:

> I really want to figure this out, as it is a barrier to using/purchasing

an application that I would otherwise buy without hesitation.

quote:

>
> many, many thanks in advance
>
>
>

subgenius webforumsuser@macromedia.com

2003-11-27, 6:44 pm

Hello, thanks for your response.

My OS is XP Home
my Av software is Avast Home [although it was disabled via task manager]
no firewall
no other background programs running, except explorer shell [again all disabled via task man]
no DW extensions installed
no network shared drive
no local files on shared or firewalled drives
no tweak installations installed
site caching was done prior to these problems
never ever had any crash/instabilities with any other applications lately
have made no changes/installations to OS in some time

I was able to run DW, but not create a new document:
when I created a new document, and then closed it via either the File>Close menu, or,
the document close button, the application crashed. In the case of
the new document being closed via the File menu, it generated a javascript
error before crashing, with the new document being closed via the document buttons,
it generated a memory reference error before crashing.

The only thing that I did to DWMX 2004 before this, was to define a local site, which
is just a usual run of the mill site setup with PHP Apache server settings, and the ftp
info. This setup wizard ran through it with no complications,and the site data was stored ok.
Then I tried t create a new doc to check out the default DW snippets. When I tried to exit without
any saved changes [as I was just checking out the snippets anyways], the above behaviors happened.

many thanks again in advance,

r41d3n

2004-03-02, 12:28 am

In DW 2004 MX I have had the crashing problem that many people have run
into. At least in my case I seem to have isolated the problem. One of my sites
had
the character " ? " contained within that. I changed it to a "e" and I haven't
had the crash to
desktop error since. Just thought I would share my experience.