Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.4.1p4
Issue ID
845223
Regression
No
Standalone build with Graphics job enabled leaks memory
Reproduction steps:
1. Open the project provided
2. Enable Graphics job (Experimental) in player settings
4. Open Task Manager
3. Build and play it
4. Wait for build to fully initialise
-Observe the memory increasing at 4-16 kb/s in Task Manager's Details tab
Note: With Graphics job disabled memory usage stops growing after Unity is fully initialised (it takes a few seconds)
Reproduced on: 5.6.0a1, 5.4.2p1 ,5.4.1p4
Graphics job is not available in 5.3 and 5.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [WebGPU] error with compute shader and read-only RWTexture
- Capacity-size memory is copied instead of Length-size when using UnsafeUtility.memCpy()
- Console displays "SerializedObjectNotCreatableException: Object at index 0 is null" error during Unity theme change while "Tile Palette" window is opened
- Details are not shown when Error Message is still selected after changing Log Entry Count in the Console
- Disabling Unity VCS in Project Settings unfocuses the Project Settings Window
Add comment