Open Bug 1741149 Opened 3 years ago Updated 10 months ago

updateBrowserRemoteness throws intermittently

Categories

(Firefox :: Tabbed Browser, defect)

defect

Tracking

()

ASSIGNED

People

(Reporter: jstutte, Assigned: nchevobbe)

References

Details

Attachments

(1 file)

There is a series of intermittents that carry a similar sequence of events:

[task 2021-11-10T11:51:23.357Z] 11:51:23     INFO - PID 8821 | [Parent 8821, IPC I/O Parent] WARNING: Failed to launch tab subprocess: file /builds/worker/checkouts/gecko/ipc/glue/GeckoChildProcessHost.cpp:750
[task 2021-11-10T11:51:23.364Z] 11:51:23     INFO - PID 8821 | JavaScript error: chrome://browser/content/tabbrowser.js, line 1909: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]
[task 2021-11-10T11:51:23.367Z] 11:51:23     INFO - PID 8821 | JavaScript error: chrome://browser/content/tabbrowser.js, line 1909: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.removeProgressListener]
[task 2021-11-10T11:51:23.594Z] 11:51:23     INFO - PID 8821 | 1636545083586	Marionette	ERROR	TypeError: can't access property "addMessageListener", this.mm is null(chrome://remote/content/marionette/dom.js:50:5) JS Stack trace: WebElementEventTarget@dom.js:50:5
[task 2021-11-10T11:51:23.594Z] 11:51:23     INFO - PID 8821 | switchToTab@browser.js:398:26
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | GeckoDriver.prototype.setWindowHandle@driver.js:1232:35
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | GeckoDriver.prototype.switchToWindow@driver.js:1172:18
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | despatch@server.js:306:40
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | execute@server.js:279:16
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | onPacket/<@server.js:252:20
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | onPacket@server.js:253:9
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - PID 8821 | _onJSONObjectReady/<@transport.js:500:20
[task 2021-11-10T11:51:23.596Z] 11:51:23     INFO - NoSuchWindowException on command, setting status to CRASH
[task 2021-11-10T11:51:23.597Z] 11:51:23     INFO - TEST-UNEXPECTED-CRASH | /service-workers/service-worker/state.https.html | expected OK
[task 2021-11-10T11:51:23.598Z] 11:51:23     INFO - TEST-INFO took 617ms
[task 2021-11-10T11:51:23.604Z] 11:51:23     INFO - PID 8821 | 1636545083604	Marionette	INFO	Stopped listening on port 47567
[task 2021-11-10T11:51:23.784Z] 11:51:23     INFO - PID 8821 | WARNING: A blocker encountered an error while we were waiting.
[task 2021-11-10T11:51:23.787Z] 11:51:23     INFO - PID 8821 |           Blocker:  SessionStore: flushing all windows
[task 2021-11-10T11:51:23.788Z] 11:51:23     INFO - PID 8821 |           Phase: quit-application-granted
[task 2021-11-10T11:51:23.788Z] 11:51:23     INFO - PID 8821 |           State: {"total":-1,"current":-1}
[task 2021-11-10T11:51:23.788Z] 11:51:23     INFO - PID 8821 | WARNING: TypeError: can't access property "sendAsyncMessage", mm is null

The tabbed browser related message points to aBrowser.webProgress.removeProgressListener(filter); with filter being null, apparently.

It might well be just a symptom of other things going wrong earlier, but it looks like updateBrowserRemoteness could benefit from some hardening regarding missing filters/listeners in any case.

Blocks: 1741017
Blocks: 1738817, 1740873
Blocks: 1738771
Blocks: 1739537, 1734283
Blocks: 1724556, 1610444
Blocks: 1725437, 1724834
Blocks: 1727855, 1738766
Blocks: 1725106
Blocks: 1727538, 1724437
Blocks: 1736301, 1725062
Blocks: 1738818, 1727486
Blocks: 1727288, 1732097
Blocks: 1738508, 1737907
Blocks: 1739612, 1694370
Blocks: 1728207
Blocks: 1740654, 1726330

This is just a symptom of the failed process launch before. We still might want to improve robustness here, too, but it is not blocking anything.

See Also: → 1741152

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)
Severity: -- → N/A
Flags: needinfo?(dao+bmo)

After enabling Fission for devtools tests, we started having several intermittent failures for this error, which also seem to impact other components than devtools: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=nsIWebProgress.removeProgressListener&list_id=16001529

In our tests, it seems that the failure usually happens when starting a test and opening a tab using BrowserTestUtils.addTab, although I'm unable to reproduce locally.

See Also: → 1756591

This is guarding on the existence of the listeners we're trying to remove.

Assignee: nobody → nchevobbe
Status: NEW → ASSIGNED
See Also: → 1760260
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: