Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
6000.4.0a1
Issue ID
UUM-124939
Regression
No
System reaches high memory usage and crashes when building with ECS-baking
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open Build Profiles
3. Observe that the Scenes "Scenes/GameBootstrapScene”, "Levels/worldBlockout_mk2/Scenes/persistent_scene", "Levels/worldBlockout_mk2/Scenes/world_scene", and "Levels/worldBlockout_mk2/Scenes/world_scene/worldscene_entityscene" are selected in the Scene List
4. Build
5. In Task Manager, observe the memory usage after 5 - 10 minutes
Expected result: Build succeeds
Actual result: RAM usage of 64 GB is reached, which crashes the system
Reproducible with: 1.3.14 (6000.0.46f1) (user reported)
Reproducible on:
Windows 11 (10.0.26100) 64bit (user reported)
Testing environment: Windows 11 (10.0.26100) 64bit (user reported)
Not reproducible on: No other environment tested
Notes:
- CQA was not able to reproduce this with AMD Ryzen 7 5800 and AMD Radeon RX 6800 XT
- User reported reproducing with a 96 GB workstation, which crashes at 64 GB RAM usage
- Not reproducible when running build through CLI (around 5 to 10Gb memory usage)
- Not reproducible with 3x3 grid (used ~29Gb memory)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Add comment