Closed kd-11 closed 7 years ago
The memory leak is confirmed now so a fix should be coming soon. It looks like there are lost refs in the texture cache. Strange thing is that it doesnt seem to happen with openGL based on reports. Can you confirm openGL isnt leaking textures?
There are textures that seldom fail to render (rendering as only black or white) or are rendered with an entirely different game texture in OpenGL, but nothing that seems to ever result in high GPU memory usage. Game map area 'Ymir Valley 1' is the best reproduction example area in where the Vulkan memory leak kills the game on a 1GB video card in just a few seconds when the snowflakes start to fall, yet in OpenGL it will run for hours with the GPU memory usage bouncing all over the place though never exceeding 3/4 of GPU memory usage. (per reporting observed of the Nvidia X Server Settings control panel.)
@greentop Looks like it isnt a memory leak afterall - the cache just uses too much VRAM. This is a good thing since it means tweaks will fix it as opposed to leaking where the data is of unknown origin.
Most of the remaining issues have been fixed recently and the ones remaining can have dedicated trackers instead of this meta-bug tracker. As such I will close this discussion.
@raveskirza Soul calibur 2 should be fixed with https://github.com/RPCS3/rpcs3/pull/3638
@kd-11 Fixed
Duplicated here too:
After exiting game through "Options" - "Quit Game" main menu screen is flickering. It happens each time and can be easily reproduced.
It starts after merging fbo_fixes, so probably is an issue.
The bug with weapon transparancy in FEAR is still there, alrhough not that apparent.
Tracker for any regressions introduced after merging https://github.com/RPCS3/rpcs3/pull/3458