When the fps drops down to 27fps from the report above, that's when high cpu usage starts.
And yep looking at the PosixTimestamp in sleep_until after that point, they are in the past (so app is spinning - hence the high cpu usage).
Decreasing the size of the window helps.
It may be indeed this driver doesn't like swapInterval 0.
When the fps drops down to 27fps from the report above, that's when high cpu usage starts.
And yep looking at the PosixTimestamp in sleep_until after that point, they are in the past (so app is spinning - hence the high cpu usage).
Decreasing the size of the window helps.
It may be indeed this driver doesn't like swapInterval 0.