Closed
Bug 164671
Opened 24 years ago
Closed 24 years ago
Mozilla 1.0 crashed after normal web activity
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ctammaro, Assigned: asa)
Details
Stack dump output below:
MOZILLA caused a general protection fault
in module GDI.EXE at 0014:00000469.
Registers:
EAX=000002ff CS=04d7 EIP=00000469 EFLGS=00000213
EBX=0000ffff SS=5257 ESP=00006e3c EBP=00006e92
ECX=00000002 DS=4387 ESI=00000662 FS=0000
EDX=00000294 ES=50d6 EDI=00000ca0 GS=059f
Bytes at CS:EIP:
66 ab 8b 46 d2 83 e0 07 88 46 b5 8b 76 c2 8b c6
Stack dump:
000008b0 00030000 0100059f 000000fe 000000f8 00000c00 0008065f 00000000 00000000
ffff0000 6e90ffff 00020c9c 000005aa 06602157 50d60000 00000c9a
wrong product. not enough information. please use talkback
Component: Bugzilla: Keyword & Component → Browser-General
Product: mozilla.org → Browser
QA Contact: timeless → asa
Comment 2•24 years ago
|
||
Reporter stated the browser crashed!
Severity --> Critical
Severity: major → critical
Comment 3•24 years ago
|
||
-> invalid
Reporter:
Please read :
http://www.mozilla.org/quality/bug-writing-guidelines.html
We need more informations in a bug report.
We fix random crashes if you use a talkback enabled build and you send the crash
reports.
You should file a bug report if you can reproduce a crash.
But you must add clear steps who to reproduce this crash.
It would be also nice if you add a Talkback ID from this crash in the bug report.
After talkback submitted the crash run mozilla/components/talkback.exe to get
the ID.
BTW: Please ask if Mozilla crashes very often and you must restart win95 and you
use an nvidia based graphic card.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•