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
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
- MultiColumnListView causes a memory leak when repeatedly shown and hidden
- Position Node with Object Space has a wrong value when there are multiple active GameObjects with the same shader
- [URP][RG] Fullscreen blit is not working when Render Graph is enabled
Resolution Note:
User needs to change how the target EntityCommandBufferSystem is created