261529 - Mozilla Suite 1.8a4 crashes on exit, with memory could not be 'read' error.

Status: RESOLVED DUPLICATE of bug 119034

(SeaMonkey :: General, defect)

Description

[Jord van der Elst]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040924
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040924

The latest Mozilla Suite 1.8a4 crashes with a memory could not be 'read' error
when you exit it. I have enabled Talkback, but it won't come up after Mozilla
has the exit crash. 

Reproducible: Always
Steps to Reproduce:
1. Start Mozilla
2. Immediately exit it
3. It will crash




I have added a picture (png format) to show the correct error message and memory
addresses, especially since Talkback doesn't want to kick in.

Comment 1

[Jord van der Elst]

Attachment: memory could not be 'read' error message.

Comment 2

[Jord van der Elst]

I've uninstalled the version above and installed the latest nightly, Mozilla/5.0
(Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040925. 

The problem seems to have gone away. I'll be leaving the bug in for now, though. 

Comment 3

[Boris Zbarsky [:bzbarsky]]

Is this an issue with a current build, then?

Comment 4

[Jord van der Elst]

My current build (2004092505) has some other crashes (I sent a Talkback report),
but the memory could not be 'read' error was for the build of the day before
that. I'll test out a new build tonight, to check its internals. 

Comment 5

[Ian Macfarlane]

I also have this in Mozilla Firefox (PR 0.10.1 overwritten with Moox PR 0.10.1
M2 build) on two machines. Various extensions on each.

XPCOM:EventReceiver: firefox.exe Application Error

The instruction at "0x00706768" referenced memory at "0x0186ec28". The memory
could not be "read".

(I would assume that the areas of memory referred to change each time but I've
not checked)

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Adam Guthrie]

*** This bug has been marked as a duplicate of 119034 ***