accessible/tests/mochitest/actions/test_treegrid.xul and cause a bunch of: ASSERTION: XPConnect is being called on a scope without a 'Components' property because one of its nsTreeView or nsTreeTreeView objects seems to stay registered with a tree (which gets painted) after the window in which it was created has been closed. In particular, the object looks like this (per js_DumpObject): object 0xab64c558 class 0x34a4380 Object flags: delegate own_shape properties: enumerate "mTree": slot 2 enumerate "selection": slot 1 enumerate "mData": slot 0 proto <Object at 0xab64c5a0> parent <Window object at 0xab63ab68> slots: 0 = <Array object at 0xab64ca68> 1 = <TreeSelection object at 0xab61fa80> 2 = <BoxObject object at 0xab634a80> The same problem seems to also happen (for one such object, multiple assertions for that object, just like the one above) in: chrome://mochitests/content/a11y/accessible/attributes/test_obj.html chrome://mochitests/content/a11y/accessible/attributes/test_text.html chrome://mochitests/content/a11y/accessible/relations/test_update.html and for many different objects in: chrome://mochitests/content/a11y/accessible/states/test_aria.html chrome://mochitests/content/a11y/accessible/table/test_headers_ariagrid.html chrome://mochitests/content/a11y/accessible/tree/test_txtcntr.html

Is it a script (mochitest) issue or it's more likely accessibility keeps reference to nsITreeView after the window was closed?

I suspect it's an issue with the tests, but I'm not certain.

dbaron, do you stil see this?

clearly doesn't happen on tbpl, and I've never seen it locally so -> WORKSFORME please reopen if you still see it