Open Bug 1815649 Opened 2 years ago Updated 2 years ago

image decoder threads are no longer named ImgDecoder so profiler doesn't pick them up

Categories

(Core :: Gecko Profiler, defect, P3)

defect

Tracking

()

Tracking Status
firefox-esr102 --- affected
firefox109 --- wontfix
firefox110 --- wontfix
firefox111 --- wontfix
firefox112 --- wontfix

People

(Reporter: tnikkel, Unassigned)

References

(Regression)

Details

(Keywords: regression)

When they got moved to taskcontroller they lost their name. The thread names now appear to be ex "TaskController #7". These threads aren't used exclusively for any one type of task anymore I take it? Should we just change the profiler ui to record TaskController threads when ImgDecoder threads are checked?

TaskController is already listed, so I guess this means we can just remove the "ImgDecoder" checkbox. Bug 1746197 comment 3 had suggestions for new thread names that might be worth listing. I would personally vote for "IPC I/O" as any delay on these threads can quickly cause significant issues elsewhere.

Summary: image decoder threads are no longer named ImgDecoder → image decoder threads are no longer named ImgDecoder so profiler doesn't pick them up

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

:bas.schouten, since you are the author of the regressor, bug 1672597, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

Probably don't need to needinfo Bas for this.

Flags: needinfo?(bas)

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

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.