Search Issue Tracker
Not Reproducible
Votes
2
Found in
2017.1.0a1
2017.1.0f3
Issue ID
931625
Regression
Yes
Shader.EditorCompileVariant in 2017.1 takes more time than in 5.6 on large projects
To reproduce:
1. Open project(link in edit) on 2017.1.0f3
2. Open profiler
3. Play 'Stage 1 mechanical' scene (use WASD and mouse button for contol)
4. Notice that sometimes editor has 0.5-2 seconds 'hiccups'
5. Repeat these steps with 5.6.2f1 or 5.6.2p3
Expected vs actual: on 5.6 'hiccups' are always 20-70ms smaller than on 2017.1 or 2017.2
Reproduced: 2017.1.0f2-f3, 2017.2.0b2
Not reproducible: 5.6.2f1, 5.6.2p3
Regression introduced 2017.1.0a1
Comments (2)
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
shihui142857
Dec 18, 2018 08:25
2017.4.14f1 ----- cause 100 ms in deep profile
Spiral-Organ
Nov 30, 2017 06:39
Present on Unity 2017.3.0b7 as well. Causes very extreme lag spikes (pauses) for a split second. Can be very disorienting to players in a mouse orbit HUD game,