Closed Bug 24246 Opened 25 years ago Closed 25 years ago

Invalid Page Fault when default home page loads

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 98
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: GDP852, Assigned: leger)

References

(
URL
)

Details

I am using the browser on top of AOL 5.0 and about halfway through the loading
of the default home page for the very first time, I get an invalid page fault.
I have not tried to type in any URLs yet.  The homepage renders as it should and
about halfway through the rendering, I recieve the following IPF:

MOZILLA caused an invalid page fault in
module GKHTML.DLL at 0167:60213ddf.
Registers:
EAX=006d91b0 CS=0167 EIP=60213ddf EFLGS=00010212
EBX=006d91b0 SS=016f ESP=0063cf2c EBP=0063cf60
ECX=00000000 DS=016f ESI=60bc594f FS=1987
EDX=0063cf2c ES=016f EDI=60bc5ad1 GS=0000
Bytes at CS:EIP:
89 41 50 c2 04 00 ff 35 14 12 29 60 83 c1 c4 ff
Stack dump:
602091e9 006d91b0 00000000 00000000 006d9174 60be7c20 00000004 00000040 00000001
00000000 00000000 00000000 01fa3dd0 0063cfc0 601eee83 00728154

I then click the "Close" button and the program closes as one might typically
expect.
GDP852@aol.com, what Mozilla build were you using when you filed this bug
report? M12? Did this happen more than once? Does this happen with M13?
And does the page continue to load properly after the error?

Assigning all open "nobody@mozilla.org" bugs to "leger@netscape.com" to weed 
thru.
Assignee: nobody → leger
GDP852@aol.com:  could you download a newer version of Mozilla (M13 or one of 
the recent nightly builds) and let us know if this still happens on your 
system?


See: http://bugzilla.mozilla.org/show_bug.cgi?id=19314

Please get latest build at:
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/

All should be fine.  MArking WorksForMe
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Marking Verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.