[thelist] Dreamweaver 8 Memory Error

Ken Schaefer Ken at adOpenStatic.com
Sun Apr 30 22:09:42 CDT 2006

:  -----Original Message-----
:  From: thelist-bounces at lists.evolt.org [mailto:thelist-
:  bounces at lists.evolt.org] On Behalf Of Jono
:  Subject: Re: [thelist] Dreamweaver 8 Memory Error
:  > The instruction at "0x5ad71531" referenced memory at "0x0000000014".
:  > The memory could not be "read". Click on OK to terminate the
:  > program.

This is most likely a bug in Dreamweaver, or some 3rd party code loaded
inside the Dreamweaver process. It looks like a standard AV (Access
Violation). If you enable the Dr Watson post mortem debugger, you can get a
dump, and use a debugger to determine what's going on. However you will
probably need to talk to Macromedia to get access to debug symbols for
Dreamweaver. In any case, you will probably need to get a fix from either
Macromedia, or (if the fault is in 3rd party code) the 3rd party vendor.

The following KB articles may be of assistance:

Description of the Dr. Watson for Windows (Drwtsn32.exe) Tool

After Dr Watson has created the user dump file, you can run Drwatsn32.exe,
and view the crash dump you have created or load it in WinDBG or similar

:  I think its just Window's terrible inability to properly handle RAM...
:  I  have 2GB and it's not enough to keep apps running without useless
:  error messages like the one your described.

Windows XP handles "RAM" just fine. Unless you have some more specific

:  I'm no Windows Pro, but messages like that tend to appear (for me)
:  when Windows fails to feed the in-use application with the required 
:  amount of RAM.  If you have multiple applications open, that may be 
:  the culprit too...if you are using a Mac (are you?) then you must 
:  have very little RAM.
:  Either way, get more RAM if possible.

All user mode applications in Windows NT/2000/XP see 4GB of virtualized
memory. None of these applications have any knowledge of real RAM. They are
presented with an independent 4GB of virtual memory, of which 2GB of reserved
for kernel use, and 2GB is usable by the actual application (well, for 32bit
platforms anyway. 64bit obviously changes that equation).

So, adding more RAM may do nothing. In fact the entire premise that your
argument is based upon is completely incorrect.


More information about the thelist mailing list