Search Issue Tracker
Fixed
Fixed in 2022.3.60f1, 6000.0.42f1, 6000.1.0b10, 6000.2.0a7, 7000.0.0a22
Votes
0
Found in
2021.3.49f1
2022.3.59f1
6000.0.40f1
6000.1.0b8
6000.2.0a4
Issue ID
UUM-98890
Regression
No
The Input system will stop responding to events when the number of handled inputs goes beyond 2^31
How to reproduce:
1. Open the “InputBufferBug,zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Select the “InputSpammer“ in the Hierarchy
5. Wait until the int field reaches “2,147,483,647“
6. Focus on the Game view
7. Press the white button at the center of the Game view (put the resolution to “4K” in case the button does not appear)
8. Observe the Console
Expected result: Nothing is logged
Actual result: An “Event in buffer is already marked as handler“ error is being constantly logged
Reproducible in: 1.7.0, 1.13.0 (2022.3.58f1, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- To reproduce, while the inputs are being spammed, the PlayerLoop has to stay active (Keep Editor focused)
- Reproducible in Player, and I suspect it might be reproducible on other platforms as well
- After exiting Play Mode, the Errors keep being thrown
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment