Search Issue Tracker
Fixed in preview.6 - 0.1.0
Votes
0
Found in [Package]
preview.0 - 0.0.4
Issue ID
1218957
Regression
No
[Unity Netcode] Constant InvalidOperationException error spam after calling World.Dispose
How to reproduce:
1. Open user's attached project (unity_delete_world.zip)
2. Enter Play mode
Expected result: Created worlds are successfully disposed
Actual result: Constant InvalidOperationException spam when calling the Destroy() method
Reproducible with: 2019.3.2f1, 2020.1.0a23 (with all package versions)
Unity Netcode package was introduced in 2019.3
Three types of errors include these:
InvalidOperationException: Unity.NetCode.ClientPresentationSystemGroup has already been destroyed. It may not be used anymore.
InvalidOperationException: Unity.NetCode.ClientInitializationSystemGroup has already been destroyed. It may not be used anymore.
InvalidOperationException: Unity.NetCode.ClientSimulationSystemGroup has already been destroyed. It may not be used anymore.
Notes:
- The Destroy() method in the attached project goes through all previously created worlds and disposes them
- Latest Unity Netcode package depends on at least Entities preview.4 - 0.3.0, tests were done on Entities preview.17 - 0.5.0
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
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
- TableEntryAdded event is not triggered when a new entry is added in the Localization Tables window
- The macOS Player is built to a different folder than the selected one when the Player is built on Windows
- Editor memory leak in VisualElement when recompiling in a blank URP project
Resolution Note (fix version preview.6 - 0.1.0):
Fixed in com.unity.netcode 0.1.0