Open Bug 1519117 Opened 5 years ago Updated 2 years ago

[remote-dbg-next] Cleanup sw registration errors logged while using about:debugging

Categories

(DevTools :: about:debugging, enhancement, P3)

enhancement

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.

Not entirely happy with this, and I seem to be getting empty fronts in listAllWorkers now.
Not flagging for review yet, waiting to see the results on try.
Priority: -- → P3

filter on: remote-debugging-m2-reserve-cleanup

Whiteboard: remote-debugging-technical-debt
Attachment #9035656 - Attachment is obsolete: true
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: