Mike Conley (:mconley) (:⚙️) Reporter
	Description • 8 years ago

The work that was landed in bug 1310880 does a good job of collecting thread hangs that occur between the point where we request to force paint, and the next time JS is interrupted so that we can paint.

However, it doesn't account for the possibility that the paint will occur before JS is even run.

We should account for that.

	Bill McCloskey [inactive unless it's an emergency] (:billm)
	Comment 3 • 8 years ago
mozreview-review

Comment on attachment 8803487 [details]
Bug 1312080 - Repeated calls to BackgroundHangMonitor::NotifyWait shouldn't unnecessarily wake the BackgroundHangThread.

https://reviewboard.mozilla.org/r/87734/#review86712

	Bill McCloskey [inactive unless it's an emergency] (:billm)
	Comment 4 • 8 years ago
mozreview-review

Comment on attachment 8803488 [details]
Bug 1312080 - Tell the BackgroundHangMonitor for force paint in the content process to wait after the next paint, even if we weren't interrupting JS. "

https://reviewboard.mozilla.org/r/87736/#review86716

	Pulsebot
	Comment 5 • 8 years ago

Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/24bfff012930
Repeated calls to BackgroundHangMonitor::NotifyWait shouldn't unnecessarily wake the BackgroundHangThread. r=billm
https://hg.mozilla.org/integration/autoland/rev/c4eee1d6a915
Tell the BackgroundHangMonitor for force paint in the content process to wait after the next paint, even if we weren't interrupting JS. r=billm"

	Ryan VanderMeulen [:RyanVM]
	Comment 6 • 8 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/24bfff012930
https://hg.mozilla.org/mozilla-central/rev/c4eee1d6a915