Closed
Bug 1896395
Opened 9 months ago
Closed 9 months ago
Allow overriding profiler threads in the URL
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
128 Branch
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: padenot, Assigned: padenot)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•9 months ago
|
||
Unfortunately writing a test for this isn't easy in the current state of things
because the threads passed to the profiler API aren't surfaced.
Assignee | ||
Comment 2•9 months ago
|
||
The goal is to diagnose a media bug with this:
about:logging?modules=HTMLMediaElement:4,HTMLMediaElementEvents:4,cubeb:5,PlatformDecoderModule:5,AudioSink:5,AudioSinkWrapper:5,MediaDecoderStateMachine:4,MediaDecoder:4,MediaFormatReader:5,GMP:5,EME:5,FFmpegVideo:4&profiler-threads=media-playback
where most modules are from the media-playback
logging preset, and the threads from the Media Playback
profiler preset.
Pushed by padenot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/670ec5c88399
Allow overriding profiler threads in the URL. r=julienw DONTBUILD
Comment 4•9 months ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 months ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•