Search Issue Tracker
Fixed
Fixed in 6000.0.75f1, 6000.3.15f1, 6000.5.0b7, 6000.6.0a4
Under Consideration for 6000.4.X
Votes
1
Found in
6000.0.69f1
6000.3.11f1
6000.4.0f1
6000.5.0a9
6000.6.0a2
Issue ID
UUM-137871
Regression
No
AccessibilityHierarchy throws an exception when Node ID reaches int.MaxValue
How to reproduce:
1. Open the attached “IN-136066” project
2. Open the scene “SampleScene”
3. Enter Play mode
4. Wait for Node ID range end to reach int.MaxValue (2147483647 nodes)
5. Observe the Console
Actual result: Exception error appears in the Console
Expected result: No errors appear in the Console
Reproducible with: 2023.2.0b8, 6000.0.71f1
Not reproducible with: 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Could not test with: 2023.1.0a1 (Accessibility Module was made discoverable in 2023.2.0b8)
Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environments tested
Note: Exception that appears in the Console: “Could not generate unique node for hierarchy. A hierarchy may only have up to 2147483647 nodes.”
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
Resolution Note:
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.6.0a4):
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.5.0b7):
Fixed in 6000.5.0b7
Resolution Note (fix version 6000.3.15f1):
Fixed in 6000.3.15f1
Resolution Note (fix version 6000.0.75f1):
Fixed in 6000.0.75f1