Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
1
Found in
6000.0.53f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
6000.4.0a1
Issue ID
UUM-110767
Regression
No
Crash on GraphicsBuffer:InternalSetNativeData when loading a specific scene
How to reproduce:
1. Open the attached “IN-103306.zip” project
2. Observe the crash
Reproducible in: 6000.0.0b13, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Could not test with: 2022.3.64f1, 2023.3.0a2 (compilation errors)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of stacktrace:
{noformat}0x00007FFD85318A8D (Unity) memcpy
0x00007FFD82AD3865 (Unity) GfxDeviceClient::WriteBufferData
0x00007FFD81A3774C (Unity) GraphicsBuffer_CUSTOM_InternalSetNativeData
0x0000023D299BF805 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.GraphicsBuffer:InternalSetNativeData_Injected (intptr,intptr,int,int,int,int)
0x0000023D299BF753 (Mono JIT Code) UnityEngine.GraphicsBuffer:InternalSetNativeData (intptr,int,int,int,int){noformat}
Comments (1)
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Gjinius
Aug 02, 2025 13:38
Same Guy here. The problem with the fps dropping whenever the cam(with the listener) is moved, was due to having selected gameobjects with the audiosource component. I suppose the graph within the audiosource component is really expensive. Thats why the fps dropped when I moved the listener. It needed to adjust the graph whenever the distance of the listener to the audiosource was changed. Though i still dont know what happened with the vsync crash there.