Stacktrace is not available for in-memory cached scripts
Categories
(DevTools :: Netmonitor, defect)
Tracking
(firefox-esr140 unaffected, firefox152 unaffected, firefox153 fixed, firefox154 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox152 | --- | unaffected |
| firefox153 | --- | fixed |
| firefox154 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
When the Stencil navigation cache is enabled (bug 1670403), the netmonitor doesn't show the stacktrace for the script request.
So far the following seems to be the place where the stacktrace is set.
That sounds like it should hook into http-on-resource-cache-response or maybe a new notification for the cached response,
and extract the stack trace there.
switch (topic) {
case "http-on-opening-request":
case "document-on-opening-request": {
...
case "network-monitor-alternate-stack": {
...
this._setStackTrace(id, stacktrace);
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 1•2 months ago
|
||
Comment 3•2 months ago
|
||
| bugherder | ||
Comment 4•2 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: If the Stencil navigation cache pref is enabled:
- Discord stops working
- DevTools Network monitor doesn't show the stack trace for cached script requests
The pref is disabled by default on non-nightly right now, but we're planning to perform an experiment there.
(same situation as bug 2042605)
- Code covered by automated testing?: no
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing: none
- Risk associated with taking this patch: low
- Explanation of risk level: This delays the script processing, which is in between the "pref is disabled" situation and the "unpatched, pref is enabled" situation.
- String changes made/needed?: none
- Is Android affected?: yes
| Assignee | ||
Comment 5•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D306595
Updated•2 months ago
|
Updated•2 months ago
|
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
Comment 7•1 month ago
|
||
Oops, I didn't mean to put the bug in the Regressed By field. I meant Depends since its building on top of code added in bug 2043993
Comment 8•1 month ago
|
||
Set release status flags based on info from the regressing bug 2027803
Description
•