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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment