Search Issue Tracker
In Progress
Votes
0
Found in [Package]
1.3.10 - Entities
7000.0.0a1
Issue ID
ECSB-1578
Regression
No
Memory leak when "WorldUpdateAllocator" fails to rewind after a Scene rebake
Reproduction steps:
1. Open the attached “repro_IN-96103“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. In the Hierarchy, select “Subscene → Cube → Sphere“
4. Open the Scene view and move around the “Sphere“ GameObject
5. Observe the Console
Expected result: An error indicating an exception is thrown due to “WorldUpdateAllocator“ being rewound after a rebake
Actual result: No errors are thrown, which signals a memory leak
Reproducible with: 1.3.10 (2022.3.59f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6)
Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environments tested
Note: User points out that if you would make this baking system allocate 1 MB every update using the “WorldUpdateAllocator” method instead, you would see the memory grow consistently until the Subscene would be closed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Add comment