Firefox

Chrome

I even tried to refresh firefox 1 more time but it;s staying like this.It's acting as if hardware acceleration is disabled when it's actually enabled (on firefox)
Or is this normal for firefox?
It is generally normal on FireFox because FireFox use bigger Meltdown/Spectre javascript clock fuzzing, 1ms (FireFox) versus 0.1ms (Chrome) -- a security method to make things difficult for hackers. So those 1ms spikes are normal on FireFox and Safari.
Forum Rules wrote: 1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
2. Please report rule violations If you see a post that violates forum rules, then report the post.
3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!
Out of curiosity.How accurate is the visual frame skipping indicator?The magenta box on the bottom right I mean.Chief Blur Buster wrote: ↑14 Sep 2025, 18:27It is generally normal on FireFox because FireFox use bigger Meltdown/Spectre javascript clock fuzzing, 1ms (FireFox) versus 0.1ms (Chrome) -- a security method to make things difficult for hackers. So those 1ms spikes are normal on FireFox and Safari.
That being said, there's a workaround with a higher-security TestUFO that unlocks a more precise clock, in terms of HTML5 APIs available to web developers.
The upcoming TestUFO 2.2 upgrades the clock source (the best possible security sandbox JavaScript can give permits a higher precision clock source) -- with 5 microsecond on Chrome and 20 microsecond on FireFox/Safari. This will hide that 1ms noise.
It's very accurate once you know how to use it. It's a benchmark for browser and OS compositor performance. Sometimes OS compositors will frameskip even when the browser think it's not, so that's why it was added. It commonly happens with multimonitor systems, for example.
Forum Rules wrote: 1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
2. Please report rule violations If you see a post that violates forum rules, then report the post.
3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!
So I should be focusing on the graph itself then instead of the magenta box?Chief Blur Buster wrote: ↑21 Sep 2025, 13:37It's very accurate once you know how to use it. It's a benchmark for browser and OS compositor performance. Sometimes OS compositors will frameskip even when the browser think it's not, so that's why it was added. It commonly happens with multimonitor systems, for example.
Ignore the regular flicker (that's designed to do that), and only focus on the erratic flickers in the VIsual Frameskipping Indicator.
1. If red spikes syncs with the erratic flickers (and the bottom part turned yellow/red), the browser successfully self-detected the frame skip.
2. If no red spikes occured (and the bottom part stayed green) while you saw an erratic flicker, the browser did not self-detect the frame skip.
Item 2 is a bigger cause for concern than item 1.
To be clear:
Forum Rules wrote: 1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
2. Please report rule violations If you see a post that violates forum rules, then report the post.
3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!