Closed Bug 1866818 Opened 1 year ago Closed 4 months ago

Ensure JS Tracer work with remote debugging

Categories

(DevTools :: Debugger, task)

task

Tracking

(firefox130 fixed)

RESOLVED FIXED
130 Branch
Tracking Status
firefox130 --- fixed

People

(Reporter: ochameau, Assigned: ochameau)

References

Details

Attachments

(2 files)

The current status of JS Tracer when remote debugging is unknown.
It isn't explitly disabled, but the preference gets in the way of using it as you need to set it manually both on desktop and the mobile device.

It would be nice to have a sanity check done by a test and if we don't plan to enable the pref soon, may be make the pref be client side only so that we can more easily use this feature.

Otherwise, the current two outputs may not be ideal for remote debugging.

  • stdout may be too complex to use as you would have to use adb logcat
  • webconsole may be too slow because of RDP latency over the wire
    An optimized custom view in the debugger may help and/or the profiler output.
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/401731aebe9b [devtools] Enable the JS tracer on remote debugging. r=devtools-reviewers,devtools-backward-compat-reviewers,nchevobbe
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: