GFX Bench T-Rex benchmark running at 57 FPS or less. Wayland HWC2 Device restarting several times
Current on Linux 4.19 and greater, both on Chromebooks and Pixel 4 devices the GFX Bench T-Rex benchmark is running at 57 FPS or less when it should be running at 60 FPS. While trying to debug this issue we noticed that Wayland HWC2 Device was restarted several times. Could these restarts be causing T-Rex to run at 57 FPS instead of 60 FPS?
To gather the data we run the command 'adb shell dumpsys SurfaceFlinger' before running T-Rex and immediately after running T-Rex on both a Pixel 4 and a Chromebook running Android 9 inside of ARC++. On the Pixel there are no restarts before running T-Rex, but 4 after running T-Rex. On the Chromebook there are 2 restarts before, but 6 restarts after. Do you know what could be causing these restarts?
I have attached the output from the command 'adb shell dumpsys SurfaceFlinger' below. Searching for 'Wayland HWC2 Device' then it should take you to the area where the restarts are shown.
adb_shell_dumpsys_SurfaceFliger_before_Trex_Pixel4_4.19.txt
adb_shell_dumpsys_SurfaceFliger_after_Trex_Pixel4_4.19.txt
adb-shell-dumpsys-surfaceflinger-before-trex_Chromebook_4.19.txt
adb-shell-dumpsys-surfaceflinger-after-trex_Chromebook_4.19.txt
adb-shell-dumpsys-surfaceflinger-after-trex-5-min_Chromebook_4.19.txt