Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.0.0
Issue ID
ECSB-539
Regression
No
Memory leak occurs in Play Mode when a GameObject is in a Sub Scene
How to reproduce:
1. Open the “UCG_DOTS“ project
2. Change “Leak Detection Level” to “Enabled With Stack Trace” (Edit > Preferences > Jobs)
3. Open the “SampleScene”
4. Enter Play mode and observe the Console
How to reproduce in new project:
1. Create a new project with the “3D Core” template
2. Add the Entities Package (Window > Package Manager > Unity Registry)
3. Wait until Burst compiles all libraries
4. Change “Leak Detection Level” to “Enabled With Stack Trace” (Edit > Preferences > Jobs)
5. Create a new Sub Scene (right-click in Hierarchy > New Sub Scene > Empty Scene)
6. Add a Cube GameObject in the Sub Scene (right-click on Sub Scene > GameObject > 3D Object > Cube)
7. Enter Play Mode and observe the Console
Expected result: no messages about memory leaks are logged
Actual result: “Found 4 leak(s) from callstack:” messages are logged
Reproduced with: 1.0.8, 1.0.11 (2022.3.5f1)
Reproduced on: Windows 11
Notes:
1. Could not reproduce in Player
2. Memory consumption is about 3 Gb in Play Mode while in Player memory consumption is about 300 Mb
3. Full memory leak message can be found in internal comments
Comments (1)
-
GameCodeurStudent
Oct 05, 2023 11:04
I will try to learn Raylib untill this issue is fixed.
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
Do not observe the memory leak problem with Entities package 1.2. I believe the memory leak issue has been fixed in Entities 1.2.