Please prefer using "Windows 10" capture method reather than "BitBlt" when using 1903 or newer Windows version

tom25519

New Member
I using VMware Workstation Pro, but I trouble with VMware memory leak. https://community.broadcom.com/vmwa...cessary-library-loading-in-vmware-workstation said

I would like to report a potential bug or unusual behavior that may be affecting the performance of VMware Workstation.


It appears that the executable mksSandbox.exe is loading the library graphics-hook64.dll from OBS Studio, if the library exists. When this library is loaded, it seems to cause increased RAM consumption and may slow down the overall performance of VMware Workstation. However, if the library is not present, VMware operates without any issues.


I am unsure why mksSandbox.exe is attempting to load this library, as it does not seem necessary for the functionality of VMware Workstation. The loading of this library appears to be an unnecessary overhead that could be avoided.
"the hook will load into any Vulkan applications by design. Setting an environment variable "DISABLE_VULKAN_OBS_CAPTURE" should prevent it from loading."



The graphics-hook64.dll is a dynamic link library associated with OBS Studio that can cause crashes in Vulkan applications, particularly when using features like Direct Display. Issues often arise when OBS is installed, even if it is not actively running, leading to problems in other applications that utilize Vulkan.

So I have to set an environment variable "DISABLE_VULKAN_OBS_CAPTURE". But when I choose "Automatic" and "BitBlt" capture method, it couldn't work - vm screen is blank, when I choose "Windows 10", it could properly work. My system is Windows 11 Enterprise LTSC 2024 x64 (24H2), newer than Windows 10 1903, I think OBS should prefer using "Windows 10" capture method reather than "BitBlt" when using 1903 or newer Windows version.
 

Attachments

  • BitBlt.png
    BitBlt.png
    95.4 KB · Views: 1
  • Windows 10.png
    Windows 10.png
    166 KB · Views: 2
  • Automatic.png
    Automatic.png
    82.4 KB · Views: 2

tom25519

New Member
Note: this is mention to "window capture", not "display capture". It seems that "display capture" has been using DXGI, which low resource usage than "Windows 10".
 
Top