Lag seems to cause key release events to be missed

[makoConstruct]

Bevy version

[[package]]
name = "bevy"
version = "0.7.0"

Operating system & version

Debian Linux, Wheezy

What you did

Ran a debug build of alien_cake_addict on my ancient gtx 980 (760?). Tried to play.

What happened

The framerate was low (maybe around 20fps). The keys tended to get stuck, in a sense, I would run in one direction for a bit, I would release the key, I'd press other directions, but the alien would not stop running in that direction, could not be turned. It would eventually stop pushing in that direction, seemingly at random, usually after the nearest cake had been tragically missed.

Oddly, the game also seemed to be harder with the lag (as if there were was less time to get each cake)

I can't think of a reason this amount of lag should cause this, but it seems to, and that makes me worry that sometimes it might miss key state changes at a normal framerate too, or during a lag spike.

Additional Information

Sometimes when my entire system is lagging, key repeats will occur. I wouldn't expect this to be the same issue though.

[TheRawMeatball]

Run in release mode instead. Rust debug builds are notoriously slow and bevy suffers these issues too. As for when making your own games, the tips in here: https://bevy-cheatbook.github.io/pitfalls/performance.html will likely be useful.

[makoConstruct]

I did also try it in release mode, and performance was fine, and no key events were dropped. That doesn't solve the problem: Some amount of lag is often inevitable no matter how well a game is optimized, and dropping key events during those times seems bad and unnecessary.

[makoConstruct]

related comment about input being dropped. Is running a faster polling loop really a sensible solution to this issue?/bug? #1343 (comment)

[geirsagberg]

Related problem, seems to be an issue whenever key repeat rate is faster than fps: #5909

[alice-i-cecile]

Consolidating with #5984.