Closed Bug 1929007 Opened 3 months ago Closed 3 months ago

Store console API calls in recorded tracing profiles

Categories

(DevTools :: Debugger, enhancement)

enhancement

Tracking

(firefox134 fixed)

RESOLVED FIXED
134 Branch
Tracking Status
firefox134 --- fixed

People

(Reporter: ochameau, Assigned: ochameau)

References

Details

Attachments

(1 file)

Thanks to bug 1828100, we can now easily store all console API calls into the profiler records by toggling logging.console pref to 5.

Because the tracer actor runs in the content process, the preference toggling logic
has to be done in some code running in the parent process: TargetConfiguration.

Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0a603b65c102 [devtools] Collect console API calls when tracing from DevTools. r=dthayer
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch

We got a regression from this (or Bug 1929004). I'm not filing a bug as it seems expected to get a regression as we're collecting more things, but it may be nice to check if we were expecting changes of that magnitude


Ratio Test Platform Options Absolute values (old vs new)
437% damp jstracer.profiler-collection-performance.DAMP linux1804-64-shippable-qr e10s fission stylo webrender 142.58 -> 765.49
338% damp jstracer.profiler-collection-performance.DAMP macosx1015-64-shippable-qr e10s fission stylo webrender 98.48 -> 431.40
337% damp jstracer.profiler-collection-performance.DAMP macosx1015-64-shippable-qr e10s fission stylo webrender 99.32 -> 433.94
271% damp jstracer.profiler-collection-performance.DAMP windows11-64-shippable-qr e10s fission stylo webrender 64.34 -> 238.70
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: