Search Issue Tracker
Fixed
Fixed in 1.3.0
Votes
0
Found in [Package]
1.2.0
Issue ID
N4EBUG-77
Regression
Yes
"System.InvalidOperationException" and "System.IndexOutOfRangeException" errors spammed in the Console when pressing "DC All" or "Reconnect all" buttons in PlayMode Tools window
How to reproduce:
1. Open the attached "ReproProjectErrors.zip" from Google Drive link
2. Enter the Play mode
3. Make sure that PlayMode Tools window is open
4. In PlayMode Tools window select "DC All" button
5. Observe the errors in the Console window
6. In PlayMode Tools select "Reconnect All"
7. Observe more errors in the Console window
Expected result: No errors in the Console window when pressing "DC All" or "Reconnect All" buttons
Actual result: Errors are spammed in the Console window when pressing "DC All" or Reconnect All" buttons
Reproducible with: 2023.3.0a17 (1.2.0-pre.4)
Not reproducible with: 2023.3.0a17 (1.1.0-pre.3)
Errors:
{code:java}
System.InvalidOperationException: The specified Unity.Entities.Editor.HierarchyNodeHandle does not exist in the hierarchy.
{code}
{code:java}
System.IndexOutOfRangeException: Index 1041062439 is out of range in container of '229' Length.
This Exception was thrown from a job compiled with Burst, which has limited exception support.
{code}
Reproduced on: macOS Sonoma 14.0 (M1)
Not reproduced on: Ubuntu 22
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.3.0):
We believe two probable causes for this have been fixed, as repro fails in 1.3.x branches.