DisplayFusion RSS: DisplayFusionService Memory/Handles

RE: DisplayFusionService Memory/Handles

Binary Fortress Software — Thu, 01 Dec 2022 18:42:27 GMT

This issue should be fixed up in the latest beta, available here: https://www.displayfusion.com/Download/Beta. Please let me know if you still run into any trouble after updating.

Thanks!

RE: DisplayFusionService Memory/Handles

Binary Fortress Software — Wed, 12 Oct 2022 20:41:25 GMT

We've found the handle leak here and it will be fixed up for the next beta

Edit: Our devs asked me to say thanks for tracking that down, your guess about the audio polling being the source of the leak was spot on 👍

RE: DisplayFusionService Memory/Handles

Binary Fortress Software — Fri, 07 Oct 2022 18:19:45 GMT

Thanks! I'll pass this over to our devs to check out

RE: DisplayFusionService Memory/Handles

Binary Fortress Software — Fri, 07 Oct 2022 10:44:36 GMT

Thank you for the response.
I was able to upload a memdump just now.
DisplayFusionService in this case is sitting at ~800MB memory and 17000 Handles
Seems like BFAudio:UpdateCachedDeviceList is leaking / recreated all the time.

This might be related to "Elgato WaveLink" Program for Audio-Channels. As The program (WaveLink) could run into a state where it would consume ~1 CPU core randomly for some time. Possibly then caused by DisplayFusion or vice versa.
Process is called AudioRoutingHelper.exe

Eglago WaveLink seems to have problems with an audio channel resulting in a loop of the following messages. That might explain why something breaks

System.Runtime.InteropServices.COMException (0x88890004): Ausnahme von HRESULT: 0x88890004
bei .()
bei .get_()
==================================================================================================================
================================================== 23:37:39.133 ==================================================
SESSION STATE CHANGED: Session: Name: "Firefox"; Parent Device: "Wave Link Browser (Elgato Wave:1) {0.0.0.00000000}.{909af04d-7842-4099-986c-b81a54e82b25} Browser"; State: Expired; ProcessID: 4332
Notified State (may differ from current/actual State): Active
REMOVED SESSION from Parent Device
==================================================================================================================
================================================== 23:37:39.135 ==================================================
System.Runtime.InteropServices.COMException (0x88890004): Ausnahme von HRESULT: 0x88890004
bei .()
bei .get_()

RE: DisplayFusionService Memory/Handles

Binary Fortress Software — Wed, 05 Oct 2022 20:25:58 GMT

Definitely sounds like a handle leak somewhere! Could you send us a memory dump when the memory usage of DisplayFusionService.exe is over 500 MB?

When the memory usage is over 500 MB, open the Windows Task Manager, click the processes tab, then right-click DisplayFusionService.exe and choose "Create Dump File"
ZIP the dump file to reduce the size
Send us the dump file via this page: https://www.binaryfortress.com/Data/Upload/

Thanks!

DisplayFusionService Memory/Handles

Binary Fortress Software — Tue, 04 Oct 2022 16:56:54 GMT

Hey,

im running into the problem that over time DisplayFusionService.exe uses about 1,3 GB of memory and has >50.000 Handles open in Task-Manager.
(Win 10 Pro 10.0.19044; DisplayFusion Pro 10 Beta 17).

I did not find out what makes it go that high yet but I can reproduce an increase of about ~300 each time I go into hibernate-mode and turn the pc back on. Memoryusage/Handles increases every time.

Example of a freshly stared DisplayFusionService:
1. About ~500 Handles initially
2. After 3-4 hibernate + reboot we get the first screenshot
3. After another reboot we get the second screenshot
4. After restarting the DisplayFusionService we get the third screenshot.

(I cannot upload the full DisplayFusionDebugInfo but these might be relevant)
Processes has ~4096 of these

Process Manager: Main Filenames [Cache_GetProcessMainFileName]: 300 seconds [6450]

1200 [281,015s / 300 seconds]: -
1200 [281,015s / 300 seconds]: -
1200 [281,015s / 300 seconds]: -

Log contains a lot of these:

2022/10/04 17:36:48.5841##_##INFO:L1##_##displayfusionservice.exe:8424##_##DFRemoteHandlers:IsFileRunning:13##_##-##_##Path: 'C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_9751f6c72c23c322\nvsmartmaxapp64.exe'##_##-
2022/10/04 17:36:48.6315##_##FAIL:L1##_##displayfusionservice.exe:8424##_##BFProcessHelpers.Static:GetProcessMainFileNameOldMethodNOCACHE:71##_##-##_##PID: 268, Zugriff verweigert, [System.ComponentModel.Win32Exception]##_##-
2022/10/04 17:36:48.6481##_##FAIL:L1##_##displayfusionservice.exe:8424##_##BFProcessHelpers.Static:GetProcessMainFileNameOldMethodNOCACHE:71##_##-##_##PID: 3096, Zugriff verweigert, [System.ComponentModel.Win32Exception]##_##-
2022/10/04 17:36:48.6556##_##INFO:L1##_##displayfusionservice.exe:8424##_##DFRemoteHandlers:IsFileRunning:29##_##-##_##Not Running: 'C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_9751f6c72c23c322\nvsmartmaxapp64.exe'##_##-
2022/10/04 17:37:48.5233##_##INFO:L1##_##displayfusionservice.exe:8424##_##BFIpc.Server:StartIpcHandlerWorkerTHREAD:108##_##-##_##IPC Received: DFServiceAction##_##-