Search Issue Tracker

By Design

Votes

1

Found in

2022.3.61f1

6000.0.48f1

6000.1.1f1

6000.2.0a10

6000.3.0a1

Issue ID

UUM-104069

Regression

No

Crash on memcpy when entering the Play Mode in a specific project

-

Reproduction steps:
1. Open the attached “repro_IN-98961“ project
2. Open the “Assets/Test Scene/Test Scene.unity“ Scene
3. Enter the Play Mode
4. Observe the crash

Reproducible with: 2022.3.61f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Couldn’t test with: 2022.1.0a1-2022.2.0a15 - Unresolvable package errors (from Entities, Collections, and Test Framework packages)

Reproducible on: Windows 10 (22H2), Windows 11 (24H2)
Not reproducible on: macOS Sequoia 15.3 (M2 Ultra)

First few lines of the stack trace:
0x00007FF812033A86 (Unity) memcpy
0x00007FF80F7E5465 (Unity) GfxDeviceClient::WriteBufferData
0x00007FF80E7491DC (Unity) GraphicsBuffer_CUSTOM_InternalSetNativeData
0x0000028B593BFC65 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.GraphicsBuffer:InternalSetNativeData_Injected (intptr,intptr,int,int,int,int)
0x0000028B593BFB83 (Mono JIT Code) UnityEngine.GraphicsBuffer:InternalSetNativeData (intptr,int,int,int,int)

  1. Resolution Note:

    Upon investigation, the issue stemmed from a custom array used within the project. This can be resolved by utilizing Unity's NativeArray or DynamicBuffer.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.