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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version preview.6 - 0.1.0):
Fixed in com.unity.netcode 0.1.0