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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment