Closed
Bug 1548373
Opened 6 years ago
Closed 6 years ago
Track network request associated with XHR responses
Categories
(Core :: Gecko Profiler, enhancement, P3)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
mozilla71
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: bas.schouten, Assigned: bas.schouten)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Right now when inside the JS stack trace for an XHR response it's really hard to track back what network request it was associated with, and it is therefore hard whether it's timing is determined by when the JS execution is scheduled, the network request was dispatched or how long the actual response took. It would be great if the two were connected.
Priority: -- → P3
Updated•6 years ago
|
Blocks: network-markers
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Assignee: nobody → bas
Status: NEW → ASSIGNED
Comment 2•6 years ago
|
||
For anybody interested, here's the PR to display these causes in the frontend: https://github.com/firefox-devtools/profiler/pull/2220
Pushed by bschouten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3d5a0f11a222
Report Open stacks for XHR responses. r=mayhemer,julienw
Comment 6•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in
before you can comment on or make changes to this bug.
Description
•