WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: jwatt, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

2 years ago
Very early during startup I get the following in the console:

WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
WARNING: No active window: file js/xpconnect/src/XPCJSRuntime.cpp, line 1421
Hm, that appears to be the slow script dialog firing. Is startup taking a very long time (i.e. longer than 10 seconds)?

If not, it would be useful to break at that warning site and capture relevant state to see how we got there.
Also, the threshold should actually be 20 seconds (the default value for dom.max_chrome_script_run_time), since we shouldn't be evaluating any content scripts so early in startup.
(Reporter)

Comment 3

2 years ago
(In reply to Bobby Holley (busy) from comment #1)
> Hm, that appears to be the slow script dialog firing.

I'm not seeing this regularly, and I've been debugging a startup crash which has involved setting breakpoints that are hit early in the startup process. It may well have been only in these cases that I was seeing these warnings. There has been so much noise in the console during startup that I've been filing bugs against I may have failed to notice that.
If you were setting breakpoints you'd definitely see this - generally disabling the slow-script dialog while debugging is a good thing to do.

Please reopen if you see this again without breaking in a debugger.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.