Closed
Bug 18102
Opened 25 years ago
Closed 25 years ago
[CRASH] Crash clicking in plaintext edit window
Categories
(Core :: XUL, defect, P1)
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: akkzilla, Assigned: waterson)
Details
Attachments
(1 file)
19.93 KB,
patch
|
Details | Diff | Splinter Review |
New today: run -edit. Bring up Debug->Plaintext Editor. Click anywhere in the
text. Get a crash. It seems to be trying to update its bold button, which it
doesn't have in the plaintext edit window. Looking at Bonsai for recent
changes, I'm guessing this might be related to Hangas' changes, but cc'ing
cmanske since he might know why we're trying to update a nonexistant bold
button.
#0 0x188 in ?? ()
#1 0x40845e5e in nsXULElement::SetAttribute (this=0x8642ba0,
aName=@0xbfffec8c, aValue=@0xbfffecf4) at nsXULElement.cpp:996
#2 0x413b22b8 in nsInterfaceState::SetNodeAttribute (this=0x871e5b0,
nodeID=0x413dda39 "Editor:Bold", attributeName=0x413dda34 "bold",
newValue=@0xbfffecf4) at nsInterfaceState.cpp:398
#3 0x413b1d9a in nsInterfaceState::UpdateTextState (this=0x871e5b0,
tagName=0x413dda45 "b", observerName=0x413dda39 "Editor:Bold",
attributeName=0x413dda34 "bold", ioState=@0x871e5c4)
at nsInterfaceState.cpp:345
#4 0x413b1158 in nsInterfaceState::ForceUpdate (this=0x871e5b0)
at nsInterfaceState.cpp:140
#5 0x413b110b in nsInterfaceState::NotifySelectionChanged (this=0x871e5b0)
at nsInterfaceState.cpp:128
#6 0x410827a0 in nsRangeList::NotifySelectionListeners (this=0x8705ff8)
at nsRangeList.cpp:1328
#7 0x41081f54 in nsRangeList::TakeFocus (this=0x8705ff8, aNewFocus=0x872b5dc,
aContentOffset=313, aContentEndOffset=313, aContinueSelection=0,
aMultipleSelection=0) at nsRangeList.cpp:1137
#8 0x410818f2 in nsRangeList::HandleClick (this=0x8705ff8,
aNewFocus=0x872b5dc, aContentOffset=313, aContentEndOffset=313,
aContinueSelection=0, aMultipleSelection=0, aHint=0)
at nsRangeList.cpp:1029
Assignee | ||
Updated•25 years ago
|
Component: XP File Handling → XUL
Assignee | ||
Comment 1•25 years ago
|
||
is this linux-only? i am not seeing this problem on win32. also, i doubt that
hangas is the best person to be looking at this bug, but maybe i'm missing
something?
Assignee | ||
Updated•25 years ago
|
Assignee: hangas → waterson
Severity: critical → blocker
Priority: P3 → P1
Target Milestone: M11
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•25 years ago
|
||
looks like an XP XUL bug.
Assignee | ||
Comment 3•25 years ago
|
||
taking from hangas
Assignee | ||
Comment 4•25 years ago
|
||
ok, what's happening here is that a broadcaster is being hooked up to a
listener node that is contained in an overlay. The overlay is never resolved
into the content model, so it's discarded; i.e., the root node of the overlay
is released. This causes the listener to be destroyed. Since the broadcaster
only has a weak reference to the listener, it is left with a dangling pointer.
I think we are too eagerly adding elements from an overlay to the XUL
document's element map. We should wait until the overlay is resolved. Hyatt,
does this fix sound reasonable to you?
Comment 5•25 years ago
|
||
This issues should be fixed, but the editor should suppress the
nsInterfaceState's ForceUpdate call when we are editing text, since there's no
attributes to update!
Assignee | ||
Comment 6•25 years ago
|
||
okay, the fix for this is getting pretty involved. i've found a bunch of
commonalities between nsXULDocument::AddSubtreeToDocument(),
ProcessCommonAttributes(), OverlayForwardReference::Merge(), and
BroadcasterHookup::Resolve(). I'm refactoring this all into
AddSubtreeToDocument(), and just using that instead.
I'm worried about causing regressions, and would like to do the dumb thing
for M11 (and make editor just not set 'bold' for the plaintext editor), and
then land the XUL fix in M12.
Does this sound ok?
Reporter | ||
Comment 7•25 years ago
|
||
That's okay with me as long as we can work out a way of figuring out from
nsInterfaceState::ForceUpdate() whether we're in a plaintext editor. There
doesn't seem to be a way of getting the editor flags from outside nsHTMLEditor.
Charley?
Assignee | ||
Comment 8•25 years ago
|
||
Reporter | ||
Comment 9•25 years ago
|
||
Yes, that patch fixes the problem, and I can use the plaintext editor again, and
updating of the status bars still works in the html editor window.
Assignee | ||
Comment 10•25 years ago
|
||
I am seeing some command updating regressions in addressbook, but after talking
with hangas, I believe that these are -not- related to this change. I'll go bug
chofmann to get this fix in if somebody'll find hyatt and get him to review it.
:-)
Comment 11•25 years ago
|
||
Waterson's patch for this fixes IM crasher bug 369026
Updated•25 years ago
|
QA Contact: rickg → sujay
Comment 12•25 years ago
|
||
setting sujay as QA contact
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•25 years ago
|
||
fix checked in, r=saari
Comment 14•25 years ago
|
||
verified in 12/7 build.
Comment 15•25 years ago
|
||
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: sujay → xptoolkit.widgets
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•