Closed Bug 2047352 Opened 2 months ago Closed 2 months ago

Stacktrace is not available for in-memory cached scripts

Categories

(DevTools :: Netmonitor, defect)

defect

Tracking

(firefox-esr140 unaffected, firefox152 unaffected, firefox153 fixed, firefox154 fixed)

RESOLVED FIXED
154 Branch
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)

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.

https://searchfox.org/firefox-main/rev/1d85bc4044b2efc1f6b59e8dff45e0de9bbe353d/devtools/server/actors/resources/network-events-stacktraces.js#133-135,157,188

switch (topic) {
  case "http-on-opening-request":
  case "document-on-opening-request": {
...
  case "network-monitor-alternate-stack": {
...
this._setStackTrace(id, stacktrace);
Blocks: stencil-nav
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Pushed by arai_a@mac.com: https://github.com/mozilla-firefox/firefox/commit/d572646d59ff https://hg.mozilla.org/integration/autoland/rev/f3b397d8af2f Reflect the stack trace for the in-memory cached script in the Network Monitor. r=devtools-reviewers,bomsy,bthrall
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: If the Stencil navigation cache pref is enabled:
  1. Discord stops working
  2. 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
Attachment #9601155 - Flags: approval-mozilla-beta?
Attachment #9601155 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Type: task → defect
Keywords: regression
Regressed by: 2043993
Regressed by: 2027803
No longer regressed by: 2043993

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

Depends on: 2043993

Set release status flags based on info from the regressing bug 2027803

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: