Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.3.0b2
Issue ID
737422
Regression
Yes
Memory is continuously allocated when running a build with 'V Sync Count' set to 'Don't Sync'
Steps to reproduce:
1. Open the attached project
2. Build and run the only scene in the project
3. When running, open 'Task Manager' (attaching profiler also works)
4. Notice the memory usage of the build is continuously increasing at about 10-15 mb/minute (left open for ~20min, keeps increasing)
Note: Change 'V Sync Count' to 'Every V Blank' or 'Every Second V Blank' in Quality Settings to see the leak disappear.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
Add comment