Closed Bug 1823922 Opened 2 years ago Closed 2 years ago

Error "Missing legacy listener for tracing-state" when connecting to an older server

Categories

(DevTools :: Debugger, defect)

Product:
DevTools
Component:
Debugger
Type:
defect

Tracking

(firefox-esr102 unaffected, firefox111 unaffected, firefox112 unaffected, firefox113 affected, firefox114 affected)

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox-esr102 --- unaffected
firefox111 --- unaffected
firefox112 --- unaffected
firefox113 --- affected
firefox114 --- affected

People

(Reporter: jdescottes, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [devtools-triage])

STRs:

  • start Firefox 112 as server
  • connect to it from Firefox 113
  • open a tab toolbox from about:debugging
  • switch to debugger

In the logs we can see

console.error: (new Error("Missing legacy listener for tracing-state", "resource://devtools/shared/commands/resource/resource-command.js", 1074))

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

:ochameau, since you are the author of the regressor, bug 1803616, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

status-firefox111: --- → unaffected
status-firefox112: --- → unaffected
status-firefox113: --- → affected
status-firefox-esr102: --- → unaffected
Flags: needinfo?(poirot.alex)

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

status-firefox114: --- → affected
Whiteboard: [devtools-triage]

This is just spamming the console with no real issue triggered.
We're in the process of removing the trait in 114, and uplifting a fix would be cumbersome for no real value, so let's wontfix it

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(poirot.alex)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.