Search Issue Tracker
Fixed in 9.0.0-pre.1
Votes
2
Found in [Package]
8.0.0-pre.5
Issue ID
1391968
Regression
No
"Invalid memory pointer was detected in ThreadsafeLinearAllocator::Deallocate!" error when Sprite is in Atlas with Tight Packing
How to reproduce:
1. Open the attached project "sprite.zip"
2. Open File>Build Settings...
3. Enable Development Build
4. Build And Run the project
Expected results: The Sprite is visible on screen and there are no errors in the Console window
Actual results: "Invalid memory pointer was detected in ThreadsafeLinearAllocator::Deallocate!" errors in the Console window and the Sprite is not visible on the screen
Reproducible with: 3.0.18 (2019.4.34f1), 5.1.7 (2020.3.26f1), 7.0.3 (2021.2.8f1), 8.0.0-pre.5 (2022.1.0b4, 2022.2.0a2)
Notes: Reproducible with both Sprite Atlas V1 and V2, and only when Tight Packing is enabled
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
- Crash on Umbra::QueryExt::queryStaticShadowCasters when opening a specific project
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when opening a specific project
- Shader variants are recompiled while Building when the Platform is switched and changed back after the first Build
- Crash on memcpy when importing lightmaps after GI bake
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
Resolution Note (fix version 9.0.0-pre.1):
Fix for this issue is available on Unity 2022.2.0a16 and above