Closed Bug 1220280 Opened 9 years ago Closed 6 years ago

Consider making jank notifications (more) async

Categories

(Toolkit :: Performance Monitoring, defect)

Product:
Toolkit
Component:
Performance Monitoring
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: Yoric, Unassigned)

References

Details

As froydnj suggested in bug 1186491, we should be careful not to cause jank by posting too many jank notifications at once from the main thread.

The question remains open whether we should post a batch of nsIRunnable (with the risk of saturating the event loop), or wait until each nsIRunnable has been treated before treating the next one (with the risk of posting several alerts for the same group in a row and/or in strange orders), or yet another strategy.
about:performance is being redesigned; mass closing the bugs related to parts of the current about:performance page that we are not keeping.

Our goals with the redesign are to reduce the overhead caused by having the page opened, increase the reliability of the displayed information, and make the offered information actionable for most users. The back-end work is being tracked in bug 1419681.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.