Closed
Bug 206959
Opened 22 years ago
Closed 22 years ago
GPF - "Mozilla caused a divide error..." when loading new page
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 128961
People
(Reporter: bobk1905, Unassigned)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
On opening "author" link from http://www.online-literature.com, the new page
loaded partially but GPF'd "Mozilla caused a divide error in module <unknown>
at 0000:00000204 ..." before the page fully loaded and Mozilla hung.
Reproducible: Always
Steps to Reproduce:
1.Got to http://www.online-literature.com/ (this page lists links to authors)
2.Select a link to any author page
3.GPF as the author page opens.
Actual Results:
Opened http://www.online-literature.com and the page loaded successfully.
Selected a link (author's name - any one); the new page loaded partially but
GPF'd "Mozilla caused a divide error in module <unknown> at 0000:00000204 ..."
before the page fully loaded. The status line showed the URL of
"http//:www.burstnet.com", so it may have been attempting to load something from
that site. Mozilla hung; required reboot.
Repeated problem three times with same result.
Unable to get screen captures because of the unstable state of the PC.
Expected Results:
Expected that the "author" page would load successfully.
Comment 1•22 years ago
|
||
worksforme with linux trunk 20030522 and 1.3
Keywords: crash
Summary: GPF - "Mozilla caused a divide error..." when loading new page → GPF - "Mozilla caused a divide error..." when loading new page
What videocard do you use? There is a known bug in older drivers for Nvidia
cards that can cause this.
Reporter | ||
Comment 3•22 years ago
|
||
This sounds like a strong possibility. My video card is,
NVIDIA GeForce2 MX/MX 400
64MB
Driver = nvdisp.drv, Version 4.13.01.2183,
its not the first problem I've had with this card. Although, I didn't have the
same problem with IE6!
Thanks.
I am sure this is your problem then. If you hesitate to install new drivers, you
can try the workaround mentioned in bug 128961#c46 first.
*** This bug has been marked as a duplicate of 128961 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•