Closed Bug 415775 Opened 12 years ago Closed 12 years ago

ClearControllers() called after global scope torn down?

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set

Tracking

()

RESOLVED INVALID

People

(Reporter: neil, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: assertion, regression)

Steps to reproduce problem:
1. Open SeaMonkey Mail (problem may also occur with Thunderbird)
2. Close the window

Actual result: ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property!

Stack trace:
Break
NS_DebugBreak_P
DEBUG_CheckForComponentsInScope
XPCWrappedNativeScope::FindInJSObjectScope
GetContextFromObject
nsXPCWrappedJSClass::DelegatedQueryInterface
nsXPCWrappedJS::QueryInterface
nsXPTCStubBase::QueryInterface
nsQueryInterface::operator()
nsCOMPtr<nsIControllerContext>::assign_from_qi
nsCOMPtr<nsIControllerContext>::nsCOMPtr<nsIControllerContext>
nsGlobalWindow::ClearControllers() nsCOMPtr<nsIControllerContext> context = do_QueryInterface(controller);
nsGlobalWindow::SetDocShell ClearControllers();
docshell.dll!nsDocShell::Destroy win->SetDocShell(nsnull);
nsXULWindow::Destroy shellAsWin->Destroy();
nsWebShellWindow::Destroy return nsXULWindow::Destroy();
[rest of stack looked irrelevant]
This doesn't look like a docshell bug. Most likely DOM (global window) or xpconnect.
Component: Embedding: Docshell → DOM
QA Contact: docshell → general
Depends on: 456672
Version: unspecified → Trunk
OK, so after some thought I've decided that this bug is invalid, because controllers live on the outer window, and only chrome can add and remove them. I documented that you should remove any window controllers you add.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Depends on: 456694
Depends on: 456696
Depends on: 456860
(In reply to comment #2)
> I documented that you should remove any window controllers you add.

I added the reference to this bug/behavior to that page...
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.