Closed
Bug 1876035
Opened 1 year ago
Closed 1 year ago
Protocol error (session.subscribe): unknown error TypeError: can't access property "getActor", context.currentWindowGlobal is null registerNavigationListenerActor@chrome://remote/content/shared/js-window-actors/NavigationListenerActor.sys.mjs:54:9
Categories
(Remote Protocol :: Agent, defect, P2)
Remote Protocol
Agent
Tracking
(firefox124 fixed)
RESOLVED
FIXED
124 Branch
Tracking | Status | |
---|---|---|
firefox124 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [webdriver:m10])
Attachments
(1 file)
I got a failure report from the pdf.js folks that after upgrading Firefox to 124.0a1 some tests no longer work on some platforms.
Here a log file that shows the problem: http://54.193.163.58:8877/2a700bd7a9812d6/output.txt
Server running at http://127.0.0.1:57712/
Error while starting firefox: Protocol error (session.subscribe): unknown error TypeError: can't access property "getActor", context.currentWindowGlobal is null registerNavigationListenerActor@chrome://remote/content/shared/js-window-actors/NavigationListenerActor.sys.mjs:54:9
startMonitoring@chrome://remote/content/shared/NavigationManager.sys.mjs:115:12
startMonitoring@chrome://remote/content/shared/NavigationManager.sys.mjs:393:24
RootMessageHandler@chrome://remote/content/shared/messagehandler/RootMessageHandler.sys.mjs:70:29
_createMessageHandler@chrome://remote/content/shared/messagehandler/MessageHandlerRegistry.sys.mjs:193:28
getOrCreateMessageHandler@chrome://remote/content/shared/messagehandler/MessageHandlerRegistry.sys.mjs:147:29
get messageHandler@chrome://remote/content/shared/webdriver/Session.sys.mjs:289:41
execute@chrome://remote/content/shared/webdriver/Session.sys.mjs:270:9
onPacket@chrome://remote/content/webdriver-bidi/WebDriverBiDiConnection.sys.mjs:211:37
onMessage@chrome://remote/content/server/WebSocketTransport.sys.mjs:127:18
handleEvent@chrome://remote/content/server/WebSocketTransport.sys.mjs:109:14
I noticed that we do not run a check that the windowGlobal
is actually available. We probably should add that.
Nevertheless I do not see why this has been regressed. We haven't changed that code for quite some time.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
This failure has actually be seen only once so far. So it's not urgent to fix. Lets put into the backlog.
Whiteboard: [webdriver:m10] → [webdriver:backlog]
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Assignee | ||
Updated•1 year ago
|
Points: 2 → 1
Assignee | ||
Updated•1 year ago
|
Whiteboard: [webdriver:backlog] → [webdriver:m10]
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/42d77e7dae4b
[remote] Only register NavigationListenerActor when a window global is available. r=webdriver-reviewers,jdescottes
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox124:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 124 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•