Search Issue Tracker
Active
Votes
0
Found in
2022.3.66f1
Issue ID
UUM-119195
Regression
No
Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
How to reproduce:
1. Open the attached “IN-112769“ project
2. Open the “Scene_AR“
3. Observe the crash
Reproducible with: 2022.1.0a10, 2022.3.66f1, 2023.1.0a2
Not reproducible with: 6000.0.57f1, 6000.2.4f1, 6000.3.0b1
Fixed in: 2023.1.0a3
Reproducible on: MacOS 15.6.1 (M4), Windows 11, MacOS 26.0 (M3) (by user)
Not reproducible on: No other environments tested
Notes:
- Sometimes the crash occurs when opening the project
- The project has to be unzipped each time it is opened. The issue doesn't always reproduce consistently, especially when switching between different Unity versions.
First few lines of the stack trace:
{noformat}#0 0x00000102027b30 in GizmoBufferSizeHistory::GetBuffer()
#1 0x00000102023cf8 in gizmos::BeginGizmo(Vector3f const&, bool)
#2 0x00000102023e94 in GizmoManager::DrawGizmos(GizmoSubset)
#3 0x000001020277c0 in DrawGizmos(Camera&, GizmoSubset)
#4 0x00000100d4460c in ScriptableRenderContext::ExecuteScriptableRenderLoop(){noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Text color is incorrect when text is rendered on SubMeshUI
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
- Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
- RenderTexture is not initialized when it is set as Material's Texture
- Branch node outputs a random value instead of a constant on the false conditon
Add comment