Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
2017.1.0f3
Issue ID
931829
Regression
Yes
ProcessMouseInWindow causes CPU spikes up to 4ms on Standalone builds
Steps to reproduce:
1. Download and open the attached project
2. Open the profiler
3. Build for Standalone
4. Launch the build in windowed mode with 768p resolution or higher.
5. Move mouse in and out of window constantly
6. Obseve profiler for EarlyUpdate.ProcessMouseInWindow
Expected result: should not take almost any time to check whether mouse is in window
Actual result: process sometimes spikes up to 3-4 ms
Reproduced on 5.6.2p4, 2017.1.0f3, 2017.2.0b3
Not reproduced on 5.5.4f1
Regression introduced in 5.6
5.6 mentions the time as Unallocated time spent, but most likely the same cause.
Verified FIXED 2017.3.0b3, 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment