Closed Bug 1314594 Opened 9 years ago Closed 8 years ago

[e10s] The command getCurrentUrl can block the communication between the chrome and frame script

Categories

(Remote Protocol :: Marionette, defect)

Product:
Remote Protocol
Component:
Marionette
Platform:
x86_64
Windows
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox55 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla55
Tracking Flags:
Tracking Status
firefox55 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

(
URL
)

Details

As noticed on bug 1299216 comment 92 while writing the crash unit tests for Marionette, a call to `get_url()` can block the communication between the chrome process (driver.js) and the framescript (listener.js) in case the currently open URL is about:blank. This problem only happens for e10s mode on Windows 64 bit systems like Windows 8 and 10 (as seen on Treeherder): https://treeherder.mozilla.org/#/jobs?repo=try&revision=908e8d88290a4057414d5391c1d1ddccf6bc7cf3 Maybe this is somewhat related to bug 1312674 but it doesn't look to be a regression from bug 1261842 (make initial browser remote sooner) given that it is also failing with a Nightly build from July 25th.
Summary: [e10s] A call to get_url() can block the communication between the chrome and frame script → [e10s] A call to navigate ("get") can block the communication between the chrome and frame script
Bug 1368101 should make this go away.
Depends on: 1368101
This is actually not navigate but getCurrentUrl.
Summary: [e10s] A call to navigate ("get") can block the communication between the chrome and frame script → [e10s] The command getCurrentUrl can block the communication between the chrome and frame script
Fixed via bug 1368101.
Assignee: nobody → hskupin
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.