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
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
Add comment