https://bugs.winehq.org/show_bug.cgi?id=55818
--- Comment #29 from Zeb Figura z.figura12@gmail.com --- (In reply to Tom M from comment #28)
I've done more testing..
The memory leak occurs in 6.15, 6.10, (6.0-6.9 I could not compile due to an error in math.h. Undefined reference to `sincos'.
So I backtracked even further, memory leak occurs in 5.15, and 5.10. I attempted to compile 5.4 and then 5.0 but I run into linker problems I'm not sure how to fix.
It got me thinking.. what if it's the vulkan loaders? Is it possible to run WINE without them? Use whatever the original was? (I think it's OpenGL)
The common thread across the compilation I saw was 'vkd3d' and Vulkan loaders. My vague memory of when I was patching WINE to run DAOC back 5 or 6 years ago there were no vulkan loaders and the game ran for hours without memory leaks. I wonder if it could possibly be that?
Blaming libvulkan seems very unlikely. We only use it briefly for GPU enumeration. There is a Vulkan-based d3d renderer for Wine available in more recent versions but it needs to be explicitly enabled.
How would I go about not using vulkan loaders as a test?
Uninstall libvulkan, I guess, but I doubt it's going to matter.
/usr/bin/ld: chain.o:(.bss+0x0): multiple definition of `hInstance'; cert.o:(.bss+0x0): first defined here
You can get around this by adding -fcommon to the CFLAGS/CROSSCFLAGS.