Open Bug 1517680 Opened 2 years ago Updated 2 years ago

[remote-dbg-next] Unexpected packet error occurs when close tab which is showing normal web content

Categories

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

defect

Tracking

(Not tracked)

People

(Reporter: daisuke, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: remote-debugging-technical-debt)

STRs:
1. Open `about:debugging`
2. Open https://developer.mozilla.org in new tab
3. Close the tab which opened https://developer.mozilla.org

ER: No any error occurs.
AR: Error below was shown in console.

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))
Handler function LocalDebuggerTransport instance's this.other.hooks.onPacket threw an exception: Error: Unexpected packet server1.conn19.content-process40/contentProcessTarget1, {"from":"server1.conn19.content-process40/contentProcessTarget1","type":"tabDetached"}
Stack: onPacket@resource://devtools/shared/protocol.js:1460:19
onPacket@resource://devtools/shared/client/debugger-client.js:765:7
send/<@resource://devtools/shared/transport/local-transport.js:64:11
exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
DevToolsUtils.executeSoon*exports.executeSoon@resource://devtools/shared/DevToolsUtils.js:57:21
send@resource://devtools/shared/transport/local-transport.js:58:7
send@resource://devtools/server/main.js:1031:5
connectToContentProcess/</onMessageManagerClose<@resource://devtools/server/main.js:383:13
exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
Line: 1460, column: 19
console.error: "Handler function LocalDebuggerTransport instance's this.other.hooks.onPacket threw an exception: Error: Unexpected packet server1.conn19.content-process40/contentProcessTarget1, {\"from\":\"server1.conn19.content-process40/contentProcessTarget1\",\"type\":\"tabDetached\"}\nStack: onPacket@resource://devtools/shared/protocol.js:1460:19\nonPacket@resource://devtools/shared/client/debugger-client.js:765:7\nsend/<@resource://devtools/shared/transport/local-transport.js:64:11\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14\nDevToolsUtils.executeSoon*exports.executeSoon@resource://devtools/shared/DevToolsUtils.js:57:21\nsend@resource://devtools/shared/transport/local-transport.js:58:7\nsend@resource://devtools/server/main.js:1031:5\nconnectToContentProcess/</onMessageManagerClose<@resource://devtools/server/main.js:383:13\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14\nLine: 1460, column: 19"
After applying https://phabricator.services.mozilla.com/D15081 patch, almost same error occurs in network debugging as well.
So, the cause might be around workers.
Priority: -- → P3

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

Whiteboard: remote-debugging-technical-debt
You need to log in before you can comment on or make changes to this bug.