In my experience, this sort of unusual bug is a symptom of underlying design problems, often caused by chronically convoluted and over-layered architecture - there&#x27;s no real reason why input events at a high rate should cause behaviour different from a lower rate. If a system can&#x27;t process events as quickly as they come, then some of them should just get ignored.<p>It&#x27;d be interesting to see the cause of this bug, but more importantly how they decide to fix it.