The |refresh_rate_| variable in ui::Compositor is only updated Compositor::SetDisplayVSyncParameters() is called. This will never happen with OOP-D enabled on Chrome OS where everything vsync/begin frame related is moved to the GPU process.
Compositor::refresh_rate() is only used on Chrome OS so it's not an issue for other platforms that have OOP-D on in finch trial.
The compositor gets begin frames that contain the vsync interval (which is equivalent to the GPU refresh rate). That could be used to keep |refresh_rate_| up to date, it's just a matter of intercepting the OnBeginFrame() message from the LayerTreeFrameSinks BeginFrameSource.
Comment 1 by bugdroid1@chromium.org
, Oct 30