[Webkit-unassigned] [Bug 261031] Visible jank in 60fps animation containing 2 alternating frames, no matter of approach taken

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=261031

--- Comment #4 from Wojciech Czechowski <wojciech.czechowski at smartframe.io> ---
Did you carefully check the provided website, Simon? There are links that lead to separate codepens for each approach. You can easily remove logging part there, but I assure you, that it is not the problem here... ;) 

By the way - blocking the main thread shouldn't bother the web worker. That's why I added "block main thread" button in there - to prove, that dropped frames are not caused by it being to busy...

What's more -> for js approaches I intentionally draw number of miliseconds between current and previous frame directly on the canvases. If you look carefully, you can see, that "dropped frames effect" ( jank ) is visible even if there is less than 17ms between frames, which means, that it is not there because js can't handle calculations in time needed to accomplish 60fps.

I am totally aware, that it is hard to get zero frame drops and that there are many things going on in the browser, that may cause jank. That's why I tried few different approaches... 

Why is it happening even for embedded video? Why simple CSS animation is also struggling to render it properly? Why I can see this jank, even if each frame of requestAnimationFrame takes ~16.66ms, which is exactly as much as needed to get smooth 60fps? 

Sorry, but "Many things that may cause dropped frames" is to broad answer for my questions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230907/7bdcd333/attachment.htm>