Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.0a1
Issue ID
788812
Regression
Yes
[Windows][AMD-only] Massive memory leak when OpenGL is set as the default graphics API
Memory leak when OpenGLCore, GLES3 or GLES2 is set as the default graphics API in Windows.
Repro steps:
1. Open EmptyScene from attached project or create new empty project.
2. Open up task manager (Ctrl+Shift+Esc) and observe Unity's memory usage.
3. Make sure the graphics API in player settings is set to OpenGLCore, GLES3 or GLES2.
4. Restore down and maximize Unity's editor window (the middle button between minimize and close)
5. Observe the memory leak in the task manager.
Expected outcome: no memory leak.
Notes:
- does not repro on OSX; seems to be a Win-only issue.
- issue appears in trunk (5.5.0a1)
- does not repro in 5.3.1f1 or 5.4.0b15; 5.5-specific.
- closing the scene view seems to alleviate the issue.
- toggling the effects preview button in the scene view seems to speed up the memory leak.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment