Search Issue Tracker
Fixed
Fixed in 2022.3.11f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a6, 7000.0.0a1
Votes
0
Found in
2022.3.4f1
2023.1.3f1
2023.2.0a22
Issue ID
UUM-41478
Regression
Yes
Editor freezes when adding a new element to a list whose parent RID starts with 4, 5 or 6
Reproduction steps:
1. Open the “AddToListStripped“ project
2. In the main menu click “RhoLab”, then “State Editor”
3. In the State Editor window click “Dax Flat”, then “Door”, then “OnClicked”
4. Expand “Response” and click + to add to the list
Expected result: A new element is created
Actual result: The Editor freezes
Reproduced in: 2022.1.0a13, 2022.3.4f1, 2023.1.3f1, 2023.2.0a22
Not reproduced in: 2021.3.28f1, 2022.1.0a12
Reproduced using: Windows 10 (by reporter), macOS 13.4.1 (Intel)
Notes:
1. First few lines of what's flooded in “Editor.log” during the freeze:
/Users/bokken/build/output/unity/unity/ModuleOverrides/com.unity.ui/Editor/RetainedMode.cs line 55]
Assertion failed on expression: ‘m_ByteOffset + m_TypeTreeIterator->m_ByteSize <= m_Data->size()'
2. Also reproduced in Inspector by selecting the “InteractionDatabase.asset” ScriptableObject, expanding FactGroups, Element 0, Facts, Element 0, Rules, Element 1, Response, and clicking + to add to the list
3. If the ScriptableObject is opened in a text editor there are two rid references (i.e. the two rules)
rid: 4453235519239487651
rid: 4453235519239487717
If the first number of the second RID is changed from 4 to 8 or 7 (change it everywhere) the freeze will not reproduce. If it’s changed to 5 or 6 it will still freeze. The issue will not reproduce when deleting the rule and creating it again, because the newly generated RID will start with 8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment