Closed
Bug 168664
Opened 22 years ago
Closed 22 years ago
crash (repeatable) on page load
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 160602
People
(Reporter: gleick, Assigned: asa)
References
()
Details
(Keywords: crash, stackwanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
instruction at 0x77f83b27 tried to access memory at 0x39393939.
I've had this same crash with other sites and earlier versions. When it happens,
there's no alternative but to use IE, which has no problem at the same page.
(No idea whether this detail is relevant, but I've uninstalled the Flash plugin.)
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Updated•22 years ago
|
Keywords: crash,
stackwanted
Comment 1•22 years ago
|
||
hm, I have the sam User-Agent, the same OS and have not installed the
Flash-Plugin, too. At my PC it doesn't crash. Have you turned JavaScript off?
Comment 2•22 years ago
|
||
Reporter:
Do you get a talkback window (if you use a build with talkback)
could be related to bug 160602 (0x39393939 vs 0x39393929
(but the adress is different, CC dbradley because I'm not sure...)
The comment in the duped bug 165220#c3 has both adresses
WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Comment 4•22 years ago
|
||
Yes, this is the same. Some people get the 0x39393929 while others get 0x39393939.
For the reporter: Are you running any resident programs. JSPager is one such
culprit. You might try unloading them and see if the problem goes away.
*** This bug has been marked as a duplicate of 160602 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 5•22 years ago
|
||
Verified Duplicate.
James, thank you for this report. You have been cc'ed on bug 160602
so you can follow progress on this issue -
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•