Massive memory leak while using Vulkan with Intel HD 520

[shellashock]

Currently tested on 5.0-3813 with Intel HD 520 driver version 21.20.16.4664. My computer is a Lenovo Thinkpad E560 running the latest Windows 10 version.

Regardless of settings, my computer will rapidly max out its memory within ~5 seconds after game boot and crash or return an error like this: http://imgur.com/2kyHURf with Dolphin self terminating at the end; depending on the game.

I am suspicious that this is a driver issue with Intel and will file a bug report if this is required; but I wanted to check here first with what information I should send in and to where. I have never submitted a driver bug report before and I would like to know what should be included here to provide sufficient detail.

Any help is appreciated.

Sincerely: shellashock

[KHg8m3r]

Can you post pictures of you Graphics configs in Dolphin?
Do you have all the latest Windows Updates Installed?
Does this happen in 5.0 stable?

[shellashock]

1. Using regular JIT engine with single core (no core over/underclock) with the following graphics settings (see attached)

2. Absolutely. Pressing check updates says "your system is up to date."

3. 5.0 stable doesn't have Vulkan, but trying to play a game with 5.0-750 (first windows build with vulkan support) simply says it cannot initialize.

The oldest build I have on hand besides this one is 4.0-3036 which boots in MOST games I have but freezes or experiences the memory leak when it should be displaying anything but the splash screens (opening videos, main menu, etc.) A point to note is that it freezes or has a memory leak before anything is drawn on the screen. I will bisect further tomorrow.

[mbc07]

Try getting the latest GPU drivers directly from Intel. Keep in mind you might need to install them using the "have disk" method (Google if) if you're running an OEM driver, as the drivers from Intel website refuses to install normally on that scenario...

[shellashock]

I actually did that before posting this not too long ago. Lenovo's drivers always seem to be one release behind the generic driver; so I installed the latest generic driver with the "have disk" method. Unfortunately, both the current latest driver and Lenovo's "validated" driver both have identical symptoms.

[KHg8m3r]

What happens when you disable XFB?

[shellashock]

I just had it enabled to show the video for Pacman World 2 for testing; Real XFB enabled, Virtual XFB or XFB disabled makes no difference. Always crashes with massive memory usage on versions newer then 5.0-1500 at least and Vulkan fails to initialize using 5.0-750 (Vulkan initial addition). I am still trying to bisect to find when Vulkan is able to initialize in Dolphin and if the memory leak is still present.

[shellashock]

I finished bisecting this issue and discovered that from 5.0-750 (first Windows + Vulkan build) to 5.0-1299, Vulkan does not initialize on my system with the following error in logs: VulkanLoader.cpp:314 E[Video]: (Vulkan::SwapChain::CreateSwapChain) vkCreateSwapchainKHR failed: (-1: VK_ERROR_OUT_OF_HOST_MEMORY)

This results in a "swap chain not created" error popup.

This issue is fixed in 5.0-1301, but all builds after that will experience the massive memory leak and crash within seconds of showing anything besides a splash screen in some games like Pacman World 2, Xenoblade Chronicles and Army Men RTS (just examples).

The message in logs for these games is:
40:09:564 VulkanLoader.cpp:314 E[Video]: (Vulkan::ObjectCache::GetPipeline) vkCreateGraphicsPipelines failed: (-1: VK_ERROR_OUT_OF_HOST_MEMORY)
40:09:564 StateTracker.cpp:614 E[Video]: Failed to get pipeline object, skipping draw

repeated ad-infinitum. An important note here is these games will only have a couple repetitions of "Failed to get pipeline object, skipping draw" before it will attempt to create the graphics pipeline again.


On the other hand, some games like Super Mario Sunshine will boot and get through the splash screen, but will immediately crash with the the "MemoryMap_Setup: Failed finding a memory base." error popup the moment the opening video starts.

The message in logs for these games is:
46:46:788 VulkanLoader.cpp:314 E[Video]: (Vulkan::ObjectCache::GetPipeline) vkCreateGraphicsPipelines failed: (-1: VK_ERROR_OUT_OF_HOST_MEMORY)
46:46:789 StateTracker.cpp:614 E[Video]: Failed to get pipeline object, skipping draw
46:46:789 StateTracker.cpp:614 E[Video]: Failed to get pipeline object, skipping draw
46:46:802 StateTracker.cpp:614 E[Video]: Failed to get pipeline object, skipping draw
46:46:805 StateTracker.cpp:614 E[Video]: Failed to get pipeline object, skipping draw
...

until it displays the error popup and self terminates Dolphin. This time the game will keep failing to get the pipeline object and skipping the draw until (presumably) Dolphin realizes that Vulkan isn't running properly and self terminates.

[shellashock]

At this point, it looks like this is just an Intel driver bug. Is there any kind of log data that could be enabled to give to Intel so they could debug this issue besides what has already been said here or should I just go ask on their forums and get further directions there?

Thanks for everyone's help so far.

[KHg8m3r]

The latest Intel driver is xxxx.4678. Does this fix the issue?