Search Issue Tracker
Fixed
Fixed in 1.0.X - Entities
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-545
Regression
No
Memory leak occurs in Play Mode as Client, Server or both when using Netcode for Entities
How to reproduce:
1. Open the “Netcode_Memory_Leak“ project
2. Open the “Login“ scene
3. Enter Play Mode
4. Select “Client & Server”
5. Select “Restart”
6. Exit Play Mode
7. Repeat steps 3-6 and observe the Console
Expected result: no warnings about a leak is logged
Actual result: “Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak” warning is logged
Reproduced with: 1.0.8, 1.0.11 (2022.3.5f1)
Reproduced on: Windows 11
Notes:
1. Could not reproduce in Player
2. When testing with the Entities Package 1.0.11 Netcode for Entities Package 1.0.12 and 1.0.11 versions were used
3. Netcode for Entities Package 1.0.8 uses Logging Package 1.0.8 which throws scripting errors in the 2022.3 stream → using Logging Package 1.0.11 fixes this error
4. Sometimes it will take a while for the scene to load when selecting “Client & Server” → no warning will be logged if the scene is not fully loaded
5. Sometimes the warning might take a few tries to appear
6. Reproducible with PlayMode Type set to “Client & Server”, “Client”, and “Server”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- On Script import/reimport MonoImporter does not generate consistent results due to updating Custom packages
- [Entities Graphics] Size of the Content Update generated folder increases when changes are made to the Scene
- In Play Mode, an extra Sync Call is made every frame when a GameObject has a Rigidbody 2D component
- Crash on block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
Add comment