Windows 10: Possible BUG / memory leak when trying to print from a 32bit process on Windows10

I have a x86 application working on windows10 64 bit environment. One pf the app's features is to generate a lot of reports, so there is a lot of printing involved. However, I noticed that every time I try to use call DefaultPrintTicket on the print queue the dllhost process COM Surrogate grows rapidly in memory.

I managed to isolate the code responsible and moved it to a test WPF app. When a button is clicked this code is being fired:


var localPrintServer = new LocalPrintServer;

var oneNotePrintQueue = localPrintServer.GetPrintQueues.FirstOrDefaultp => p.Description.ContainsOneNote;

var printTicket = oneNotePrintQueue?.DefaultPrintTicket;



The printing queue is irrelevant as I tried them all and the problem remains.


I tried some tweaks in the registry i.e. finding AppId AA0B85DA-FDDF-4272-8D1D-FF9B966D75B0 and removing "AccessPermission", "LaunchPermission" and "RunAs" with no result.

Is there any way I can stop the memory leak or allow normal printing from an 32bit process?

:)

 

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.

 

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.

 

Windows Memory Leak

'Memory leak' refers to a process that continues to use memory even after the process has ended.

Since leaking memory is a coding problem (and a serious one at that) the only way to solve it is to bring it to the software developer's attention.

In the illustration accompanying your question, which process(es) is/are leaking memory?