42e24ed927
With the current stopwatch design, we request the frame rate multiple times per frame. On Android this calls into JNI which is pretty slow. If we cache the value at construction of the StopwatchVisualizer, then we will only compute it once per frame (because the StopwatchVisualizer is reconstructed each frame). Fixes https://github.com/flutter/flutter/issues/137797 So the issue isn't that we're checking the fresh rate every frame, its that we were checking N times on each frame.