Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2020.1.0a19
2021.1
2021.2
2022.1
2022.1.0a1
Issue ID
1346970
Regression
Yes
Unfreed allocations are reported after building a player and exiting Play Mode by double-clicking Scene assets
How to reproduce:
1. Create a new Unity project
2. Build the project
3. Return to the Editor and enter Play Mode
4. Double-click the SampleScene in Project View
Expected result: The scene is opened and no errors/warnings/logs are thrown
Actual result: The scene is opened, TLS Allocator error, stack allocation warnings, and unfreed allocations are reported in the Console
Reproducible with: 2020.1.0a19, 2020.3.14f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1
Not reproducible with: 2018.4.34f1, 2019.4.28f1, 2020.1.0a18
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
- Lightmaps are baked incorrectly for GameObjects when their Position is <=-2048 or >=2048 on any of the coordinates
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a3
Resolution Note (fix version 2021.2):
Fixed in 2021.2.2f1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.27f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.23f1