Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
Issue ID
UUM-36254
Regression
No
Crash when updating SerializedProperty using EditorApplication.contextualPropertyMenu
How to reproduce:
1. Open the attached project “My project (3).zip“
2. Open the custom Editor window (VSP > Report Window)
3. Right-click next to any of the list names
5. Press "Add Category"
Expected result: A new list is added
Actual result: Unity crashes
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16
Can’t test with: 2023.2.0a15 (Errors in the Console when trying to open the Report Window)
Reproduced on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
First few lines of the stack frames:
{{#0 0x00000107425800 in WalkTypeTreeInternal(TypeTreeIterator const&, unsigned char const*, int*, int, bool)}}
{{#1 0x000001074255e6 in WalkTypeTreeInternal(TypeTreeIterator const&, unsigned char const*, int*, int, bool)}}
{{#2 0x000001074255e6 in WalkTypeTreeInternal(TypeTreeIterator const&, unsigned char const*, int*, int, bool)}}
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
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.