Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.14f1
2023.2.3f1
2023.3.0a17
Issue ID
UUM-58190
Regression
No
Crash on tlsf_free when UI Elements are moved to the side by scrolling
Reproduction steps:
1. Open the “crash_prj” project
2. Open the “BeginnerMission” scene
3. Enter the Play Mode
4. Observe the crash
Expected result: The application does not crash
Actual result: The application crashes
Reproducible with: 2022.3.14f1, 2023.2.3f1, 2023.3.0a17
Could not test with: 2021.3.33f1 (error CS1061 'NavMeshSurface' does not contain a definition for 'IsPartOfPrefab' and no accessible extension method 'IsPartOfPrefab' accepting a first argument of type 'NavMeshSurface' could be found (are you missing a using directive or an assembly reference?))
Reproduced on: Windows 10
Not reproduced on: No other environments tested
Note:
- reproducible with manual scrolling by Scroll Rect (comment {{StartScrollDay()}} function in BeginnerMissionListView script and enter the Play Mode then scroll UI elements manually)
- reproducible in Player
First few stack frames:
0x00007FF6EA6A432E (Unity) tlsf_free
0x00007FF6E847F45B (Unity) DynamicHeapAllocator::Deallocate
0x00007FF6E84908CF (Unity) DualThreadAllocator<DynamicHeapAllocator>::TryDeallocate
0x00007FF6E847FCD2 (Unity) MemoryManager::Deallocate
0x00007FF6E848868A (Unity) free_alloc_internal
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
With the information provided it looks like the issue is in the user code, not in Unity.