Closed
Bug 250276
Opened 21 years ago
Closed 20 years ago
right-click, cut of BM inside folder inside PT crashes [@ nsMenuPopupFrame::SetCurrentMenuItem ] (aviary)
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: shaver, Assigned: vlad)
Details
(Keywords: crash, fixed-aviary1.0)
Crash Data
Attachments
(2 files)
8.54 KB,
text/plain
|
Details | |
1.16 KB,
patch
|
bugs
:
review+
shaver
:
superreview+
asa
:
approval1.8a6+
|
Details | Diff | Splinter Review |
It's poking at mCurrentMenu, which looks like it has been freed. No crash on
0.9.1, or the trunk.
Attaching stack.
Reporter | ||
Comment 1•21 years ago
|
||
Reporter | ||
Comment 2•21 years ago
|
||
Pretty sure we want this for 1.0, not sure if it hold 1.0RC1.
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0+
Assignee | ||
Comment 3•21 years ago
|
||
I'm guessing this is a nsIFrame-in-nsCOMPtr issue. I fixed a few of these in my
local tree, but there's at least two dozen nsIMenuFrame's that get stuck in
nsCOMPtr's in one place or another. Most look innocent, but some don't.. i'll
try to find the culprit. Also, biesinger has embarked on a
remove-nsISupports-inheritance-from-nsIFrame project, which will also help.
Status: NEW → ASSIGNED
Updated•21 years ago
|
Severity: normal → critical
Keywords: crash
Summary: right-click, cut of BM inside folder inside PT crashes: nsMenuPopupFrame::SetCurrentMenuItem (aviary) → right-click, cut of BM inside folder inside PT crashes [@ nsMenuPopupFrame::SetCurrentMenuItem ] (aviary)
Assignee | ||
Comment 4•21 years ago
|
||
Blah. The chain of events looked like this:
- A destructive context menu option is selected (Cut, Delete)
- The menu's command handler executes the command
- The command modifies the bookmarks RDF data source, and removes some
assertions from the parent RDF container (to remove the items)
- The template builder (!@#$) notices this, and sees that it has to remove
content
- It removes the menu item entry from the menu that corresponds to the thing
that was just removed
- The command returns to the menu handler after execution, and the menu starts
to tear down the visible menus
- It goes boom while trying to unselect the active menu item, because that item
got destroyed
The patch makes sure that the menu frame's parent doesn't have it selected as
the current item, if it's being destroyed.
Assignee: nobody → vladimir
Reporter | ||
Comment 5•21 years ago
|
||
Comment on attachment 152886 [details] [diff] [review]
context-menu-crash-0.patch
Looks good to me -- Ben?
Attachment #152886 -
Flags: superreview+
Attachment #152886 -
Flags: review?(bugs)
Updated•21 years ago
|
Attachment #152886 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 6•21 years ago
|
||
In on aviary; does trunk want this as well?
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•21 years ago
|
||
Yes, very. Maybe even for 1.8a2 -- asking. (If not, a3 for sure.)
Flags: blocking1.8a2?
Updated•20 years ago
|
Flags: blocking-aviary1.0PR?
Updated•20 years ago
|
Keywords: fixed-aviary1.0
Reporter | ||
Updated•20 years ago
|
Flags: blocking1.8a2?
Assignee | ||
Comment 8•20 years ago
|
||
Reopening this as it's not on trunk; need a menu person to take a look, though
this has been in on aviary for a while now.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•20 years ago
|
||
Neil, can you have a look at this for the trunk?
Comment 11•20 years ago
|
||
As far as I can tell the patch looks good for the trunk too.
Comment 12•20 years ago
|
||
Comment on attachment 152886 [details] [diff] [review]
context-menu-crash-0.patch
Who can land this? Time is short for 1.8a6. a=asa.
Attachment #152886 -
Flags: approval1.8a6+
Comment 13•20 years ago
|
||
Fix checked in to the trunk.
Status: REOPENED → RESOLVED
Closed: 21 years ago → 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Flags: blocking1.8a6?
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: xptoolkit.widgets
Updated•14 years ago
|
Crash Signature: [@ nsMenuPopupFrame::SetCurrentMenuItem ]
You need to log in
before you can comment on or make changes to this bug.
Description
•