Search Issue Tracker
Fixed
Fixed in 1.3.10 - Entities, 7000.0.0a1
Votes
0
Found in [Package]
1.3.5 - Entities
7000.0.0a1
Issue ID
ECSB-1415
Regression
No
The EntityCommandBuffer.SetSharedComponentManaged() never frees the GCHandle and causes a memory leak when setting shared component on an entity
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the MonoUsed value on the screen
Expected result: MonoUsed value fluctuates and doesn't increase forever
Actual result: MonoUsed keeps going up
Reproducible with: 1.2.0 (2022.3.52f1), 1.3.5 (2022.3.52f1)
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- EntityManager.SetSharedComponentManaged() does not reproduce the issue
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 GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note (fix version 1.3.10 - Entities):
This was fixed in com.unity.entities 1.3.10