Open Bug 1502415 Opened 6 years ago Updated 2 years ago

subprocess_worker_win.js/subprocess_worker_unix.js shouldn't be shown as High Energy impact

Categories

(Toolkit :: Performance Monitoring, enhancement)

Product:
Toolkit
Component:
Performance Monitoring
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox65 --- affected

People

(Reporter: florian, Unassigned)

References

Details

The real problem is that these workers block their execution for 5s while polling, and we count that as CPU time.

If we can't find an actual solution, we should ignore the CPU time for that specific worker in the front-end code, to avoid user confusion.
No longer blocks: new-about-performance-m1
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.