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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
Add comment