Closed
Bug 1819965
Opened 1 year ago
Closed 1 year ago
"TabSession.executeInChild" will hang if message manager has been replaced
Categories
(Remote Protocol :: CDP, defect, P1)
Remote Protocol
CDP
Tracking
(firefox112 fixed)
RESOLVED
FIXED
112 Branch
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m6])
Attachments
(1 file)
Currently we load our framescript for the content browser only once when initially creating the TabSession for a tab. But that means if the browsing context gets replaced due to a navigation the message manager is replaced as well and the new one doesn't load the framescript. As such calling executeInChild will finally end up using a dead message manager.
Fixing that gets us a bit closer to a fix for bug 1600054, but we still suffer from data loss given that all the data that we store happens inside the content process. So side-effects are expected but at least we do no longer hang.
|
Assignee | |
Comment 1•1 year ago
|
||
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e565bfdc6250 [cdp] Re-load framescript when browsing context gets replaced due to a navigation. r=webdriver-reviewers,jdescottes
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
|
|
Assignee | |
Updated•1 year ago
|
Points: --- → 2
Priority: -- → P1
Whiteboard: [webdriver:m6]
You need to log in
before you can comment on or make changes to this bug.
Description
•