Re: [e10s] Higher priority handling for vsync in child processes

vsync handling happens usually right after a task (per HTML spec). Basically we have now two event queues with similar priority, and they are handled the same priority, but since the other one is used very rarely, events added to it get processed on average sooner than the ones added to the norm

Re: [e10s] Higher priority handling for vsync in child processes

On 10/11/2016 18:12, smaug wrote: > vsync handling happens usually right after a task (per HTML spec). > Basically we have now two event queues with similar priority, and they > are handled the same priority, but since > the other one is used very rarely, events added to it get processed on > avera

Re: [e10s] Higher priority handling for vsync in child processes

On 10/11/2016 00:22, smaug wrote: > Parent process doesn't yet have higher priority handling [2]. > Need to fix racy tests first. > Locally using higher priority also in parent process seems to make tab > throbber smoother. We have an ad-hoc mechanism for scheduling memory pressure event ahead of

[e10s] Higher priority handling for vsync in child processes

Hi, the latest nightly has higher priority for vsync/refreshDriver/requestAnimationFrame handling in child processes [1], which should make rendering updates smoother, at least in some cases. If you see any unexpected behavior, please file bugs and CC me, :smaug. And if there are cases when re