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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
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,