Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a12
2020.1.2f1
2021.1
Issue ID
1275221
Regression
Yes
"Enable Full StackTraces" does not provide more details when encountering Memory leak
Reproduction steps:
1. Create an empty project
2. Enable Full StackTraces
3. Import the attached "DisposeTest.cs" Script and attach it to any active GameObject
4. Press Play and wait for a memory leak to be reported in the Console
Expected result: Additional information is provided with the error in the Console
Actual result: Error still says to "Enable Full StackTraces to get more details"
Reproducible with: 2019.1.0a12, 2019.4.12f1, 2020.1.8f1, 2020.2.0b7, 2021.1.0a1
Not reproducible with: 2018.4.28f1, 2019.1.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Add comment