Open
Bug 1672960
Opened 4 years ago
Updated 4 years ago
Network Requests with no status showing in the Network panel
Categories
(DevTools :: Netmonitor, defect, P2)
DevTools
Netmonitor
Tracking
(Fission Milestone:Future, firefox-esr78 unaffected, firefox82 unaffected, firefox83 wontfix, firefox84 wontfix, firefox85 fix-optional)
NEW
Fission Milestone | Future |
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox82 | --- | unaffected |
firefox83 | --- | wontfix |
firefox84 | --- | wontfix |
firefox85 | --- | fix-optional |
People
(Reporter: bomsy, Unassigned)
References
(Regression)
Details
(Keywords: regression, Whiteboard: dt-fission-network-monitor dt-fission-future)
Attachments
(1 file)
385.47 KB,
image/png
|
Details |
The network panel shows Network requests with no status in Nightly
STR
- Open a new blank browser tab
- Open devtools and the network panel
- Open the browser toolbox
- Enter https://www.websocket.org/echo.html
AR
Multiple request in the network panel are missing their status
ER
The Status should be showing .
Reporter | ||
Comment 1•4 years ago
•
|
||
These errors show for each of the failing request in the browser console.
Updated•4 years ago
|
Severity: -- → S3
Has STR: --- → yes
Priority: -- → P2
Comment 3•4 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d6713d75c647f4d5d5f6a85adfa146a1eeb705a5&tochange=b8c0746ee1995684b218bd85c6bd53bbc15ac44d
Regressed by: 1669545
Updated•4 years ago
|
Has Regression Range: --- → yes
Keywords: regressionwindow-wanted → regression
Reporter | ||
Comment 4•4 years ago
|
||
Looked into this with Alex, and this is likely related to early request missed before the NetworkObserver is initialized. This should likely be fixed when fission is enabled.
Depends on: 1665383
Comment 5•4 years ago
|
||
Set release status flags based on info from the regressing bug 1669545
status-firefox82:
--- → unaffected
status-firefox83:
--- → affected
status-firefox84:
--- → affected
status-firefox-esr78:
--- → unaffected
Comment 6•4 years ago
|
||
The following exception visible in the Browser Console is related:
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITraceableChannel.setNewListener]", result: 2147500037, filename: "resource://devtools/server/actors/network-monitor/network-observer.js", lineNumber: 1086, columnNumber: 0, data: null, stack: "_setupResponseListener@resource://devtools/server/actors/network-monitor/network-observer.js:1086:38\n_createNetworkEvent@resource://devtools/server/actors/network-monitor/network-observer.js:912:12\n_httpStopRequest@resource://devtools/server/actors/network-monitor/network-observer.js:409:14\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:103:22\n", location: XPCWrappedNative_NoHelper }
ThreadSafeDevToolsUtils.js:82:13
Honza
Fission Milestone: --- → MVP
Whiteboard: dt-fission-network-monitor
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Fission Milestone: MVP → Future
Whiteboard: dt-fission-network-monitor → dt-fission-network-monitor dt-fission-future
You need to log in
before you can comment on or make changes to this bug.
Description
•