Closed Bug 18829 Opened 21 years ago Closed 20 years ago

Clicking link on page crashes browser

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3, critical)

x86
Windows 95
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: ewokninja, Assigned: joki)

References

()

Details

Build ID: 1999111218

Click a link on the page crashes browser. I clicked on one of the articles in
the "top news stories" section and it crashed with the following error (hope it
helps):

MOZILLA caused an invalid page fault in
module <unknown> at 0000:00cc7553.
Registers:
EAX=00cc758c CS=0137 EIP=00cc7553 EFLGS=00010202
EBX=6025a544 SS=013f ESP=0063f0dc EBP=0063f120
ECX=0063f11c DS=013f ESI=00000000 FS=688f
EDX=00cb075c ES=013f EDI=0063f164 GS=0000
Bytes at CS:EIP:
00 8c 75 cc 00 dc 74 cc 00 8c 74 cc 00 6d 00 2d
Stack dump:
601e63a6 00e57520 00ec38c0 0063f11c 00000000 00000000 00000000 00000000 00000000
00e2bca0 00cb075c 601e7b8b 00cb0750 0063f164 00000001 6025a544
Tested it and it crashes browser in Linux as well. Wasn't able to get any
debugging output but it seems easy enough to duplicate.
Severity: major → critical
I can't get this to crash on any platform today [1999120609]
Anyone else still see it?
They've changed their layout and the latest version (as of 12/11/99) doesn't
shot that problem. Fortunately I downloaded a copy of their old page (attached)
and tried it out and it doesn't crash on that. I get something different,
however. When I click on a link on that page it brings up this dialog box which
says:

You are about to download a file of type
application/x-unknown-content-type

I guess whatever is causing that was what
was causing the older version to crash.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
I guess this needs to be marked works for me because it now does work for me.
Reopen if you can attach a testcase that shows any of the problems you had.
Status: RESOLVED → VERIFIED
works for me too
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.