1186702 - ProcessHangMonitor.jsm: TypeError: win.gBrowser is undefined

Status: NEW

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

Description

[Jesse Ruderman]

Attachment: testcase

With:
  user_pref("nglayout.debug.disable_xul_cache", true);

JavaScript error: resource:///modules/ProcessHangMonitor.jsm, line 194: TypeError: win.gBrowser is undefined

(I'm testing with e10s disabled, and popups enabled.)

Comment 1

[Jesse Ruderman]

Attachment: testcase 2 (unreliable)

Comment 2

[Jesse Ruderman]

With that one I saw both:
* win.gBrowser is undefined
* win.gBrowser is null

Comment 3

[Intermittent Failures Robot]

1 failures in 2672 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1186702&startday=2018-08-13&endday=2018-08-19&tree=all

Comment 4

[Florian Quèze [:florian]]

I saw this error today when keeping Cmd+N pressed for a few seconds to open several browser windows at once. I was on this line: https://searchfox.org/mozilla-central/rev/5e3bffe964110b8d1885b4236b8abd5c94d8f609/browser/modules/ProcessHangMonitor.jsm#410

I think gBrowser doesn't exist yet because the window hasn't finished initializing. That's likely because Services.wm.getEnumerator("navigator:browser") returns all browser windows, including the ones that aren't done loading.