Search Issue Tracker
Fixed in 2021.3.24f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a10
Votes
0
Found in
2021.3.22f1
2022.2.15f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-29271
Regression
No
Memory Leak error when no directional light is present in the Scene and Leak Detection Level is enabled
Reproduction steps:
1. Open the attached “HDRPTestProject” project
2. Open “OutdoorsScene” scene
3. Enter the Play Mode
Expected result: Play Mode is entered and continues without any errors
Actual result: Memory leak error in the Console: “A Native Collection has not been disposed, resulting in a memory leak. Enable Full StackTraces to get more details. Leak tracking may be enabled via {{Unity.Collections.NativeLeakDetection.Mode}} or from the editor preferences menu Edit > Preferences > Jobs > Leak Detection Level.”
Reproducible with: 2023.1.0b7, 2023.2.0a5
Could not test with: 2020.3.46f1, 2021.3.20f1, 2022.2.10f1 (no Edit > Preferences > Jobs > Leak Detection Level Setting)
Reproducible on: Windows 10
Not reproducible on: macOS Ventura 13.2.1 (M1 Max)
Note: Error doesn’t appear when Scene has Directional Light GameObject or it is disabled
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment