Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.5f1
2022.1.7f1
2022.2.0a17
Issue ID
UUM-8477
Regression
No
Crash on UnsafeUtility_CUSTOM_MemSet when entering Play mode
Reproduction steps:
1. Open the user’s attached project “Eo Fusion 2022.zip“
2. Enter Play mode
3. Wait a few seconds
Expected results: The Editor does not crash
Actual results: The Editor crashes
Reproducible with: 2021.3.5f1, 2022.1.7f1, 2022.2.0a17
Could not test: 2020.3.35f1, 2023.1.0a2 - due to the project opening in safe mode
Reproduced on: Windows 10 Pro
Stack trace:
0x00007ff60029e549 (Unity) UnsafeUtility_CUSTOM_MemSet
0x00000295d2dc3fb8 (Mono JIT Code) (wrapper managed-to-native) Unity.Collections.LowLevel.Unsafe.UnsafeUtility:MemSet (void,byte,long)
0x00000295d2dc3ed3 (Mono JIT Code) Unity.Collections.LowLevel.Unsafe.UnsafeUtility:MemClear (void,long)
0x00000295d2dc3e8b (Mono JIT Code) \[Native.cs:31] Fusion.Native:MemClear (void*,int)
0x00000295d2e2c7db (Mono JIT Code) \[NetworkRunner.cs:2626] Fusion.NetworkRunner:InitializeNetworkObjectState (Fusion.NetworkObject,Fusion.NetworkRunner/AttachOptions)
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:
This is not an issue in the Editor itself. A NetworkObject that is referencing invalid memory is attempting to write directly to the same invalid memory in an unsafe manner, so editor crashing (or random data corruption within the game, etc.) in this case is not an unexpected result. Likely a native resource's safety/lifetime issue exists within Fusion, or the code invoking it.