BrowserUsageTelemetry.jsm, line 108: TypeError: win.gBrowser is undefined
Categories
(Firefox :: General, defect, P3)
Tracking
()
People
(Reporter: florian, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
1.28 MB,
image/png
|
Details |
I saw this error today when keeping Cmd+N pressed for a few seconds to open several browser windows at once. It was on this line: https://searchfox.org/mozilla-central/rev/5e3bffe964110b8d1885b4236b8abd5c94d8f609/browser/modules/BrowserUsageTelemetry.jsm#108
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.
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Dexter, this is potentially skewing our data. Is this something you want to fix or should I mark it P3?
Comment 2•6 years ago
|
||
(In reply to Matthew N. [:MattN] (PM me if requests are blocking you) from comment #1)
Dexter, this is potentially skewing our data. Is this something you want to fix or should I mark it P3?
Hey Matthew, I'm redirecting this to Chris as I'm mostly on glean these days.
Comment 3•6 years ago
|
||
If this is something that only comes up when opening new windows as fast as possible there's no priority from our end :)
Reporter | ||
Comment 5•6 years ago
|
||
(In reply to Chris H-C :chutten from comment #3)
If this is something that only comes up when opening new windows as fast as possible
That's the steps to reproduce on a fast development machine.
Normal users may see this whenever opening a browser window is slow.
Comment 6•6 years ago
|
||
So it may affect the recording of browser.engagement.max_concurrent_{tab|window}_count
and browser.engagement.tab_open_event_count
by undercounting.
ni?rweiss who is the owner of those probes for what impact it might have and whether that should change the priority.
Comment 7•4 years ago
|
||
Chris, this bug came up during Firefox::General triage. Are the probes you mentioned still being recorded and are they still affected by this bug?
Comment 8•4 years ago
|
||
They are still being recorded and are still being used. If this error still manifests, they'll still be affected.
Comment 9•3 years ago
|
||
Hey florian, we tried to reproduce this but no luck. Are you still seeing it?
Reporter | ||
Updated•3 years ago
|
Updated•2 years ago
|
Reporter | ||
Comment 11•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Reporter | ||
Updated•5 months ago
|
Description
•