My client runs Publisher on machines with many CPU cores, and runs many jobs in parallel. Some of the reloads might use excessive amounts of memory , and there was no history about wich one, when, how much . So it is hard to fix.
One can see in QEMC what tasks are running, and one can use Task Manager to see how much memory is used per QVB.exe . While QVB.exe is running you can use tools as Sysinternal's Process Explorer to see what is the working directory, and thefefore know what file is reloading. But once reload is finished, you don't know anymore.