[remote-dbg-next] Cleanup sw registration errors logged while using about:debugging
Categories
(DevTools :: about:debugging, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: remote-debugging-technical-debt)
Attachments
(1 obsolete file)
Now that we support workers for most runtimes, the command line starts to be polluted with a lot of errors related to service workers.
We often see:
A promise chain failed to handle a rejection: Connection closed, pending error from root, type getProcess failed - stack
error occurred while processing 'listWorkers: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIServiceWorkerManager.getRegistrationByPrincipal]" nsresult: "0x80004005 (NS_ERROR_FAILURE)
console.error: (new Error("Unexpected packet server1.conn19.content-process40/contentProcessTarget1, {"from":"server1.conn19.content-process40/contentProcessTarget1","type":"tabDetached"}", "resource://devtools/shared/protocol.js", 1460))
This makes our logs hard to read. We already have https://bugzilla.mozilla.org/show_bug.cgi?id=1516414 for the getProcess message and https://bugzilla.mozilla.org/show_bug.cgi?id=1517680 for unexpected packet. The goal of this bug is to reduce/silence the getRegistrationByPrincipal
errors.
Reporter | ||
Comment 1•6 years ago
|
||
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 2•6 years ago
|
||
filter on: remote-debugging-m2-reserve-cleanup
Updated•6 years ago
|
Updated•2 years ago
|
Description
•