Search Issue Tracker
Active
Under Consideration for 6000.2.X
Votes
0
Found in
2022.3.63f1
6000.0.50f1
6000.1.6f1
6000.2.0b4
Issue ID
UUM-108870
Regression
No
Log “Found 1 leak(s) from callstack:“ is present in Editor when Leak Detection Level is set to "Enabled"
Reproduction steps:
1. Open the attached project "ReproProj"
2. Set Leak Detection Level to “Enable with StackTrace” (Edit > Preferences > Jobs > Leak Detection Level > Enable With Stack Trace)
3. Click Tools > Reload Domain
4. Set Leak Detection Level to “Enabled” (Edit > Preferences > Jobs > Leak Detection Level > Enabled)
5. Repeat step 3
6. Observe the Console
Expected result: No leak detections are present
Actual result: Log “Found 1 leak(s) from callstack:“ is present
Reproducible with: 2022.3.63f1, 6000.0.50f1, 6000.1.6f1, 6000.2.0b4
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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