Windows 10: Potential Memory Leak - SpatialAudioLicenseSrv.exe Zombie Processes

Recently my computer has had a Paged pool of upwards of 48GB and upon further inspection it appears that SpatialAudioLicenseSrv.exe has been creating zombie processes under svchost.exe. Does anybody know what the cause of this is and how to fix this? Thanks

:)

 

Memory leak issue

The term "memory leak" means that an application fails to return all its RAM to the operating system when it exits. The leftover RAM is unusable to the operating system.

Step one is to identify the application that is leaking memory. Step two is to contact the application's developers and provide as much detailed data on the memory leak as you can. For example: which processes are still in RAM after the application exits
and how much RAM they occupy. Application developers never want their applications to leak memory and they will be grateful for the details you provide, particularly if they can replicate the leak on their own computers.

 

Possible Memory Leaks in Windows 10

A memory leak occurs when an application closes and fails to release all its RAM back to the operating system.

The first step in dealing with a memory leak is to determine which application is leaking memory.

The next step is to contact that application's technical support with complete details of the memory leak, since the developers will want to fix the problem ASAP.

 

Windows 10 Memory Leak not visible in processes

I am currently struggling to interpret the data regarding my memory usage and my system appears to be leaking memory which is not visible within any process.

Process RAM Usage (Size):





Process RAM Usage (Percent):





RAM Usage (Resource Monitor):





As per my Resource Monitor, I have 12000+ MB of memory "in use" which is nowhere near what I see on my task manager view. Resource Monitor shows the largest contributor to Committedng.exe taking up around 1GB of Committed memory (This is not shown in Task Manager).

I have been looking around for solutions and noticed a few common useful pieces of information can be provided such as a poolmon.exe output sorted by paged data and number of bytes as can be found here.









Any suggestions on what could be causing this or any suggestions towards further diagnosing the problem would be greatly appreciated.