Closed
Bug 2239
Opened 26 years ago
Closed 26 years ago
Crash when leaving test9
Categories
(Core Graveyard :: GFX, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: pierre, Assigned: davidm)
Details
Tested with Jan7 optimized build with 10Mb partition:
- launch the app
- type cmd-9 to go to test9
- type cmd-5
==> crash
I didn't check for sure but it seemed to me that the crash was dure to leaving
test9 more than going to test5.
Reporter | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•26 years ago
|
||
Note: there is another crash with test9 (#2236) although the two don't seem to be
related.
Reporter | ||
Updated•26 years ago
|
Assignee: pierre → beard
Status: ASSIGNED → NEW
OS: All
Reporter | ||
Comment 2•26 years ago
|
||
Reassigned to beard because he already has 2236.
As far as I can tell, we are crashing because when a nsWindow is deleted, it
doesn't set the nsToolkit::mFocusedWidget to nil if it is the focused widget.
Then when the focus is set to another window, we crash and burn by sending the
deleted window a losing focus event. I don't know if the problem is that a window
should have lost focus before being deleted or that upon being deleted a window
should lose focus.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•26 years ago
|
||
Verified fixed in 2.2.99 Mac OS build (with 10 MB RAM partition.)
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•