Search Issue Tracker
Fixed in 5.3.3
Votes
2
Found in
5.2.1p3
Issue ID
736077
Regression
No
[Perf] GISceneManager.Update taking ~90% processor time on scene start
Reproduction steps:
1. Open the project "repro.zip"
2. Open the profiler, and turn on "editor profiling"
3. Open the scene "_8Artois_HIGHMEM_ASSETBUNDLE"
Notice that GISceneManager.Update() is taking ~90% of processor time.
Notice that GI isn't even turned on.
If the project is closed after the lag stops, and started again, the lag will resume.
After several minutes, the performance will return to normal. The performance hit seems to depend on the number of objects in the scene.
I've attached a screenshot of the profiler screen. [Actually, FogBugz doesn't let me attach anything ATM (503 error), so if whoever reads this needs those files, I can send them over via slack.]
Comments (4)
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
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
lrb
Apr 22, 2019 18:22
Still present at Unity 2017.4.22f1.
noobz_from_poland
Feb 26, 2018 08:34
EDY's solution works in 2017.1
Edy
Jun 14, 2017 17:02
Still present in 5.6.1p1 in large scenes with many objects.
Workaround: Lighting > disable Auto-Generate, then Generate Lighting manually.
rotor-games
Nov 23, 2015 12:14
this issue persists in 5.3.0f1, it's causing really unworkable editor performance.