214159 - seconds after browser startup, 'unreadable memory' msg appears

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[jon]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

Start browser in win2kpro on tyan S2468 dual AMD mobo with 4 gigs ram and Tyan
bios update 4.05
Seconds after startup, foll. msg returns: "The instruction at 0x75087d39
referenced memory at 0x75087d39. The memory could not be read."  .. click ok ->
mozilla exits.
Note that per the msg, the instruction location and the referenced memory are
exactly the same memory ..  It DID 'read its instruction' in order to decide
where to look for the referenced ram, and then decided it could not do what it
already had done.

Reproducible: Sometimes

Steps to Reproduce:
1.start Mozilla
2.
3.

Actual Results:  
today, 3 times in a row produced identical results.  At other times, during
browsing, Mozilla will throw up a similar 'memory unreadable' msg and then 'OK'
-> exit.  The ram location is often different.  This ram is fully tested DDR
from Crucial. It is possible this motherboard has probs dealing with 4 gigs ram.

Expected Results:  
should have properly followed a proper instruction and continued normally

Comment 1

[jon]

"Component" choice for this bug report is just a guess.  (Why not include
'Guess' in the option list when filing reports?)

Comment 2

[Aaron Leventhal]

If you click on the "Component" link, you'll get 
http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

which describes the various componentes.

Comment 3

[Jon Henry]

Until it is determined what module the code is crashing in, this component is fine.

Jon: Is this still a problem in recent Mozilla builds? Your build is now almost
3 months old and this may have been fixed. Also, were you able to submit a crash
report with the Quality Feedback Agent? If so, please report your "talkback id"
here. You can find it by looking in the Components folder under the folder where
you installed Mozilla, and running talkback.exe. This will help the developers
track down the exact line of code that is crashing. Thank you.

Comment 4

[Jon Henry]

Closing as WFM, since we haven't heard from jon in several months. This might be
related to installing over an older version. jon, if you happen to try a newer
version of Mozilla installed to a clean directory, and still are seeing this
bug, please feel free to reopen.