Protocol error (Target.setDiscoverTargets): this.browsingContext is null
Categories
(Remote Protocol :: CDP, defect, P3)
Tracking
(Not tracked)
People
(Reporter: impossibus, Unassigned)
References
Details
(Whiteboard: [puppeteer-beta-reserve] [fission-])
See https://bugzilla.mozilla.org/show_bug.cgi?id=1548592#c2
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #3)
Maja, this most likely happens when the method gets called early enough right after startup and not all browsers have been loaded in any of the tabs. Could you please check how many tabs are getting opened? If that's more than one, please try some of the Marionette/geckodriver preferences so that only a single tab is opened during startup, and as best with
about:blank
. Does that help?In any way it would be good to file it as a separate bug and mark it blocking this meta bug.
These are the prefs being used, so I think the tab/about:blank settings are taken care of: https://hg.mozilla.org/try/rev/860cece0b54ed7a7364775c22e68933e0b796822
When I watch the tests, there's one about:blank tab and one Wordpress-admin tab.
Comment 1•5 years ago
|
||
Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Maja, can you please check if that bug still happens for you?
Reporter | ||
Comment 3•4 years ago
|
||
No
Assignee | ||
Updated•4 years ago
|
Description
•