Search Issue Tracker
By Design
Votes
1
Found in [Package]
0.16.0-preview.21
Issue ID
1292310
Regression
No
[ECS] Memory leak when a World is initialized without EndSimulationEntityCommandBufferSystem
How to reproduce:
1. Open the project attached in the edit ("ecsluk.zip")
2. Enter Play mode
Expected results: JobTempAllocs don't exceed their lifetime of 4 frames and therefore become a memory leak
Actual results: Many JobTempAllocs exceed their lifetime of 4 frames as indicated by the many warnings
Reproducible with: ECS 0.14.0-preview.18 - Version 0.16.0-preview.21 (2020.1.17f1, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2)
Could not test with: 2018.4.30f1, 2019.4.18f1 (Errors downgrading)
Note:
Warning thrown informing of the leak:
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
User needs to change how the target EntityCommandBufferSystem is created