Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b3
Issue ID
868686
Regression
Yes
[Performance] Garbage collection allocation has increased substantially when loading a new scene from 5.5 to 5.6
Repro steps:
1. Open SceneController scene from attached project.
2. Make sure profiler is running and visible
3. Press Play
4. Press Right arrow button on keyboard to switch to next scene.
5. Observe spike in profiler.
6. Select spike and observe GC allocation (around 1.2 MB)
7. Compare with 5.5, the same spike is only a few kb.
Expected outcome: GC allocation to not be that large.
Notes:
- Press "R" to reload the scene and view the spike again.
- Happens with all large scenes which have many particle systems
- Did not detect noticeable overhead in scenes with fewer (5-10) systems.
- Doesn't occur in 5.5.0p3, happens in 5.6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment