Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
4
Found in
2019.3.0a2
2019.3.0f5
2020.1.0a19
Issue ID
1211383
Regression
No
Editor performance drop when holding down keys and moving mouse when in Playmode
How to reproduce:
1. Open the attached project
2. Open "SampleScene" scene
3. Windows > Analysis > Profiler
4. Switch the profiler to Editor mode
5. Enter Play mode
6. Hold down Shift+A keys and move the mouse through the Hierarchy or Game View
7. Notice the spikes in profiler
Actual result: Holding the keys and moving mouse causes significant performance drop in the Editor.
Expected result: The performance doesn't get affected.
Reproducible with: 2017.4, 2018.4, 2019.1, 2019.2, 2019.3, 2020.1.0a19.
Not reproducible with: 5.2,
Notes:
- Reproducible on both OSX and Windows
- The spikes seems to be connected to the window the mouse is on.
Comments (2)
-
rxmarccall
Jun 14, 2020 20:15
There appears to be a regression in the latest 2019.4 LTS release as I'm seeing this issue once again.
-
Peter77
Jan 16, 2020 16:40
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a24.
Resolution Note (fix version 2019.3):
fixed in 2019.3.8f1