When frame skipping is enabled, the core uses a counter to limit the number of consecutive frames that can be dropped (to prevent the display from hanging indefinitely). This counter should be reset each time that a frame is actually rendered, but due to a small oversight it is not (apologies!). This means it is possible for a frame that should be dropped to be rendered instead, once every 30 times that a frame skip is requested. Most users probably wouldn't notice this, but it's incorrect behaviour...
When frame skipping is enabled, the core uses a counter to limit the number of consecutive frames that can be dropped (to prevent the display from hanging indefinitely). This counter should be reset each time that a frame is actually rendered, but due to a small oversight it is not (apologies!). This means it is possible for a frame that should be dropped to be rendered instead, once every 30 times that a frame skip is requested. Most users probably wouldn't notice this, but it's incorrect behaviour...
This trivial PR fixes the issue.