Search Issue Tracker
Fixed
Fixed in 2021.3.43f1, 2022.3.40f1, 6000.0.13f1, 7000.0.0a1
Votes
0
Found in
2021.3.40f1
2022.3.36f1
6000.0.9f1
Issue ID
UUM-74939
Regression
No
Crash on UnsafeUtility_CUSTOM_MemSet when simulating a random tick event for a tile at a specified position
How to reproduce:
1. Open the attached "CrashRepro" project
2. Open the ”Assets/Scenes/SampleScene.unity” Scene
Reproducible with: 2021.3.40f1, 2022.3.36f1, 6000.0.9f1
Reproducible on: macOS 14.5 Sonoma (Intel), Windows 11 (reported by user)
Not reproducible on: No other environment tested
Notes:
- Removing the “position = pos;“ code in the “CustomTile“ Script will stop the crash from happening
First few lines of stack trace:
0x00007ff777da7299 (Unity) UnsafeUtility_CUSTOM_MemSet
0x000001fe1ba30f98 (Mono JIT Code) (wrapper managed-to-native) Unity.Collections.LowLevel.Unsafe.UnsafeUtility:MemSet (void,byte,long)
0x000001fe1ba30ed3 (Mono JIT Code) Unity.Collections.LowLevel.Unsafe.UnsafeUtility:MemClear (void,long)
0x000001fe2547a4f3 (Mono JIT Code) Unity.Collections.NativeArray`1<UnityEngine.Vector3Int>:.ctor (int,Unity.Collections.Allocator,Unity.Collections.NativeArrayOptions)
0x000001fe254798bb (Mono JIT Code) UnityEngine.Tilemaps.ITilemap:FindAllRefreshPositions (UnityEngine.Tilemaps.ITilemap,int,intptr,intptr,intptr)
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
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 6000.0.13f1):
Fix for this issue will be available on Unity 6000.0.13f1 and above
Resolution Note (fix version 2022.3.40f1):
Fix for this issue is available on Unity 2022.3.40f1 and above
Resolution Note (fix version 2021.3.43f1):
Fix for this issue is available on Unity 2021.3.43f1 and above