Closed Bug 1643624 Opened 4 years ago Closed 4 years ago

TypeError: can't access property "id", channel.loadInfo.browsingContext is null

Categories

(DevTools :: Netmonitor, defect, P2)

defect

Tracking

(firefox-esr68 unaffected, firefox77 unaffected, firefox78 unaffected, firefox79 fixed)

RESOLVED DUPLICATE of bug 1643713
Tracking Status
firefox-esr68 --- unaffected
firefox77 --- unaffected
firefox78 --- unaffected
firefox79 --- fixed

People

(Reporter: Honza, Unassigned)

References

(Regression)

Details

(Keywords: regression)

This looks like regression from bug 1642470

I am seeing an error in the Browser Console

TypeError: can't access property "id", channel.loadInfo.browsingContext is null
    matchRequest resource://devtools/server/actors/network-monitor/network-observer.js:119
    _httpResponseExaminer resource://devtools/server/actors/network-monitor/network-observer.js:403
    makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103

I am working on STRs...
(edit: See comment #3)

Honza

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

Tracking this regression for Fission Nightly milestone (M6c) because the regressing bug 1642470 was tracked for M6c.

Fission Milestone: --- → M6c

STR:

  1. Load https://www.bbc.com/
  2. Open DevTools Toolbox
  3. Switch to the Debugger panel (or make sure the Debugger panel is selected by default)
  4. Check the Browser Console for the error

Honza

Has STR: --- → yes

@Alex, can you reproduce this on your machine?

Honza

Flags: needinfo?(poirot.alex)

This might be fixed by Bug 1643713. i'll test to confirm.

Flags: needinfo?(hmanilla)

Yep, works for me now, thanks for the pointer.

Honza

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

Great! Thanks @honza

Flags: needinfo?(hmanilla)
Flags: needinfo?(poirot.alex)

Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.

Fission Milestone: M6c → ---
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.