Search Issue Tracker

Won't Fix

Won't Fix in 2022.3.X

Votes

0

Found in

2022.3.66f1

Issue ID

UUM-119195

Regression

No

Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene

Handles/Gizmos

-

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}

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base. This bug is only happening once in a specific project (and scene). Plus it seems the project has been opened with Unity 6 and then reopened with 2022.3 which seems to be the cause of the problem. Even though we are trying our best regarding backward compatibility, this is not something we support by default. Multiple reasons for that: Breaking API can be added between major versions, packages that might not be compatible, format of data storage that can change and not be compatible with the previous one... Regarding the specific case here and the unique repro on a single scene, we will close this ticket to prioritize other bugs.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (2022.3.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base. This bug is only happening once in a specific project (and scene). Plus it seems the project has been opened with Unity 6 and then reopened with 2022.3 which seems to be the cause of the problem. Even though we are trying our best regarding backward compatibility, this is not something we support by default. Multiple reasons for that: Breaking API can be added between major versions, packages that might not be compatible, format of data storage that can change and not be compatible with the previous one... Regarding the specific case here and the unique repro on a single scene, we will close this ticket to prioritize other bugs.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Log in to vote on this issue

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.

Latest issues

See all new issues