Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.3.0a11
Issue ID
1076716
Regression
No
Masive Scripts overhead of the Editor in the Profiler using Deep Profile
Reproduction steps:
1. Open the attached project.
2. Open Window > Analysis > Profiler.
3. Toggle on "Deep Profile' and "Profile Editor".
4. Wait for 30-60 seconds.
5. Disable and enable "Deep profile" and "Profile Editor".
6. Play for 10 seconds and stop the "MainGameScene".
Actual behavior
- Notice how Scripts resource usage ramps up (Screenshots attached).
- Most of the memory is not cleared after this.
- I was able to reach 30 GB memory usage repeating steps 4-6 on my macOS machine.
- Not reproducible with an Empty project.
- Possibly a regression.
Reproduced with:
- 2018.3.0a11 (Project doesn't work with 2018.2 and older Unity versions as there is a lot of nested prefabs)
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
- Memory leak when using Native Plugin in Windows IL2CPP Build
- [URP][Tutorial] Universal 3D Sample tutorial issues
- Gradle error: "...Unexpected error during link..." is thrown when building for Android and targeting API Level 34
- Crash on ReplaceTextureData when rapidly changing light intensity
- Uneven lighting is seen on the GameObjects when Sky Occlusion is enabled
Resolution Note:
Will be addressed as a feature as both deep profiler and Profiler Window overhead reduction requires redesign of how deep profiler works and how Profiler visualizes the data.