Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.1.0b3
Issue ID
521165
Regression
No
Editor consumes all free memory if run with Nvidia graphics
Editor consumes all free memory until it gets unresponsive and be closed only by "killing" the process. (In the attached video the speed rate of memory consumption can be seen)
This happens only when Editor is run with Nvidia graphics processor (NVIDIA GeForce GT 525M) and the second monitor attached.
How to reproduce:
- Have a laptop setup with the 2 monitor
- Open Task Manager (on one of the monitors)
- Run Unity Editor with Nvidia graphics (on the other)
- Open the attached project.and play/stop it several times.
- Watch the memory consumption
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment