Search Issue Tracker
Fixed
Fixed in 1.3.X - Entities
Votes
2
Found in [Package]
1.3.2 - Entities
7000.0.0a1
Issue ID
ECSB-1358
Regression
Yes
Memory leak warning occurs when Server Worlds are created and disposed multiple times using Entities
How to reproduce:
1. Open the attached "IN-85541" project
2. Open the "Main" Scene
3. Set the Leak Detection Level to “Enabled With Stack Trace” under Preferences > Jobs
4. Enter Play mode
5. Wait until a “Disposed” message appears inside the Console window
6. Exit Play mode
7. Enter Play mode again
8. Observe the Console window
Expected result: No memory leak occurs
Actual result: Memory leak warning appears in the Console window
Reproducible in: 1.2.4 (2022.3.50f1, 6000.0.23f1), 1.3.2 (2022.3.50f1, 6000.0.23f1)
Not reproducible in: 1.2.3 (2022.3.50f1, 6000.0.16f1)
Could not test with: 2021.3.44f1 (does not support the full release of the Entities package)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
- “ReferenceError: Pointer_stringify is not defined” error is thrown when downloading a file
- GameObjects are not rendered when using a fragment shader with RWStructuredBuffer in URP
- [Profiler] The GPU Highlight module flags the frame before the spike when using DoInference in a coroutine
Add comment