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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.