Search Issue Tracker
Duplicate
Votes
0
Found in
2021.3.16f1
2022.1.24f1
2022.2.1f1
2023.1.0a15
Issue ID
UUM-24795
Regression
No
Incorrect memory leak detection when using UnsafeUtility.CheckForLeaks() method
Reproduction steps:
1. Open the attached project “MemoryLeakBug“
2. Press “Testing>Test Leak Detection”
3. Observe the Console window
Expected result: There are no memory leaks detected
Actual result: Random count of memory leaks are detected
Reproducible with: 2021.3.16f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0b7
Not reproducible with: 2023.2.0a1, 2023.2.0a5
Couldn't test with: 2020.3.43f1 ('UnsafeUtility' does not contain a definition for 'CheckForLeaks')
Reproducible on: Windows 11
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Issue has been fixed from another ticket
Duplicate of another internal issue: UUM-29342: Native Leak Detection reports false positive leaks