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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment