Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2019.4.24f1
2020.3.4f1
2021.1.3f1
2021.2.0a12
2022.2.0b1
Issue ID
UUM-1559
Regression
No
Excesive GPU memory usage when resizing a window via dragging
How to reproduce:
1. Open the attached "Klondike.zip" project
2. Build and run on UWP
3. Choose any corner of the build window -> drag the corner to resize the window (see repro.mp4)
Expected result: GPU memory usage rises up a bit (10-30%)
Actual result: GPU memory usage rises a lot (about 40-90% depending on build complexity)
Reproducible with: 2019.4.24f1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a12
Notes:
- The issue was tested on Standalone and UWP builds
- Usage can rise up to about 90%
- The issue does not appear when minimizing and maximizing the window
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2022.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.