Why UI Animation fps drop with chromium v124

22 views
Skip to first unread message

Rahul Patel

unread,
Jul 25, 2024, 8:06:42 PM (2 days ago) Jul 25
to Chromium-dev
Hello,
I am trying to run chromium version 124 on one of the  mob device which has 2GB RAM where animation FPS it shows UI Animation at 60fps, but running the same code on another device which has 1 GB of RAM but animation FPS is limited to 30fps. but this difference i didn't noticed with chromium version 122.

I am using https://www.vsynctester.com/ page for animation calculation, on linux arch.

Wondering which layer has changes between v122 and v124 which is causing this fps difference? does anyone know the possible commits in v123 and v124 for this behaviour to change or how do we bisect bad commits at this situation?   

Could someone please help me on this? 

Thanks,
 Rahul

Alexei Svitkine

unread,
Jul 25, 2024, 10:06:49 PM (2 days ago) Jul 25
to patelrah...@gmail.com, Chromium-dev
If you're interested in bisecting to find a commit that introduced some change, see this page: https://www.chromium.org/developers/bisect-builds-py/

It has instructions on how to do precisely that.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/0efb7449-7808-43e9-8f50-ff10b12e390bn%40chromium.org.

Rahul Patel

unread,
Jul 26, 2024, 3:06:47 PM (19 hours ago) Jul 26
to Alexei Svitkine, Chromium-dev
Thanks for sharing the link Alex :) 

Using bisecting tools is very painful (we have made quite more custom changes on top of it upstream changes ) for our use-case because we need to build and run the chromium at every bad commit.

But based on the nature of this issue, it looks like there are some new commits in v123 and v124 around how to make certain rendering decisions based on available system resources ? 

Reply all
Reply to author
Forward
0 new messages