Closed
Bug 161389
Opened 22 years ago
Closed 22 years ago
browser crash on startup [@ UpdateWindowCount(WindowGroupData *, int, int)]
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 153815
People
(Reporter: lorenrosen, Assigned: Matti)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
|
10.92 KB,
text/plain
|
Details |
browser crashed due to the usual FrameChanged problem. Restarted it. It crashed
again immediately after I selected the profile to use, with a stack trace I
haven't seen before. Restarted it again, and the same thing happened. Restarted
yet again and it started without crashing.
I'm attaching a stack trace from the three crashes.
|
Reporter | |
Comment 1•22 years ago
|
||
Note there are three crashes traced here. The first is the familiar
FrameChanged crash. The other two are UpdateWindowCount
|
||
Comment 2•22 years ago
|
||
UpdateWindowCount not found in LXR...
Severity: normal → critical
Keywords: crash
Summary: browser crash on startup → browser crash on startup [@ UpdateWindowCount(WindowGroupData *, int, int)]
So, this bug is strictly about the UpdateWindowCount crashes, right? If so, you
should probably remove the other crash from your attached crash log.
|
|
Reporter | |
Comment 4•22 years ago
|
||
The question is whether the sequence of crashes is coincidence, and whether the
first stack trace would thereby hold any clues as to the cause of the later crashes.
|
Assignee | |
Comment 5•22 years ago
|
||
*** This bug has been marked as a duplicate of 153815 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
|
||
Updated•20 years ago
|
Product: Browser → Seamonkey
|
||
Updated•13 years ago
|
Crash Signature: [@ UpdateWindowCount(WindowGroupData *, int, int)]
You need to log in
before you can comment on or make changes to this bug.
Description
•