Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.47f1
2022.3.54f1
Issue ID
UUM-90920
Regression
No
Crash on SharedRendererScene::~SharedRendererScene when opening a specific scene
Reproduction steps:
1. Open the attached project "CrashRepro"
Expected result: Project opens
Actual result: Editor crashes
Reproducible with: 2021.3.47f1, 2022.3.54f1, 2023.1.0a10
Not reproducible with: 6000.0.31f1, 6000.1.0a8
Fixed in: 2023.1.0a11
Reproducible on: Windows 11
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}0x00007ff6e9899042 (Unity) SharedRendererScene::~SharedRendererScene
0x00007ff6e9898b7a (Unity) CullResults::~CullResults
0x00007ff6e9a6c369 (Unity) CleanupScriptableCullResults
0x00007ff6eb9c39d8 (Unity) Camera::ExecuteCustomRenderPipeline
0x00007ff6eb9c65fc (Unity) Camera::RenderEditorCamera
0x00007ff6eb9c7d72 (Unity) Camera::RenderEditorCamera
0x00007ff6e97086ad (Unity) Internal_DrawOutline
0x00007ff6e96dbdd5 (Unity) Handles_CUSTOM_Internal_DrawOutline_Injected{noformat}
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
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, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.
In this specific case we recommend upgrading to version 2023.1.0a11 or newer to resolve the problem.