Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.46f1
Issue ID
UUM-32159
Regression
No
Cannot see full stacktraces in console when collection is not disposed
How to reproduce:
1. Download and open the attached project
2. Open SampleScene
3. Enter and exit Play mode
Expected outcome: A full stack trace is provided in the console window
Actual outcome: 'A Native Collection has not been disposed of, resulting in a memory leak. Enable Full StackTraces to get more details.` error appears, even though full stack traces are enabled
Reproduced with: 2020.3.46f1, 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Comments (2)
-
DevDunk
Apr 24, 2023 14:44
This has to be enabled in Jobs ->Leak Detection → Full Stack Traces (expensive).
While this does solve the issue, the error is not clear and should point to this menu, as for all other errors the stack trace depth is managed in the console settings -
DevDunk
Apr 02, 2023 10:58
Found in not updated properly
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
- 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
Resolution Note:
2020.3 is out of support
Resolution Note (2020.3.X):
2020.3 is out of support