190447 - Crash attempting DOM manipulation on <tree>

Status: RESOLVED DUPLICATE of bug 184202

(Core :: XUL, defect)

Description

[[e-mail]]

Moving a <tree> to a different position in the XUL DOM causes Mozilla to crash.
Workaround: set the selection to null first, and recreate it afterwards.
[This version for a single selection tree]
var index = folderTree.currentIndex;
folderTree.view.selection = null;
// move the folder pane box (parent of folderTree) and splitter
desiredParent.insertBefore(folderPaneBox.nextSibling, desiredParent.firstChild);
desiredParent.insertBefore(folderPaneBox, desiredParent.firstChild);
if (index >= 0)
  folderTree.view.selection.select(index);

Comment 1

[Jan Varga [:janv]]

Attachment: testcase

I can't reproduce it. Is it rdfliner specific or folder pane specific ?
Could you provide a stack trace ?

Comment 2

[[e-mail]]

ASSERTION: You can't dereference a NULL nsCOMPtr with operator->().
Called from nsTreeSelection::FireOnSelectHandler() at nsTreeSelection.cpp:715
713   nsCOMPtr<nsIBoxObject> boxObject = do_QueryInterface(mTree);
714   nsCOMPtr<nsIDOMElement> elt;
715   boxObject->GetElement(getter_AddRefs(elt));
Called from nsTreeSelection::AdjustSelection() at nsTreeSelection.cpp:687
Called from nsTreeBodyFrame::RowCountChanged() at nsTreeBodyFrame.cpp:1667
Called from nsTreeBoxObject::RowCountChanged() at nsTreeBoxObject.cpp:423
Called from nsXULTreeBuilder::Rebuild() at nsTreeBuilder.cpp:1055
Called from nsXULTreeBuilder::SetTree() at nsTreeBuilder.cpp:834
Called from nsTreeBodyFrame::SetView() at nsTreeBodyFrame.cpp:703
Called from nsTreeBodyFrame::EnsureView() at nsTreeBodyFrame.cpp:601
Called from nsTreeBodyFrame::GetPrefSize() at nsTreeBodyFrame.cpp:390
...

Comment 3

[[e-mail]]

Attachment: One approach

Comment 4

[Jan Varga [:janv]]

actually this looks very similar to bug 184202

Comment 5

[[e-mail]]

No longer blocking 105542. I need to save and restore the selection to stop the
rebuild from destroying it, so I need to manually reset the tree attribute.

Comment 6

[[e-mail]]

*** This bug has been marked as a duplicate of 184202 ***