In our enterprise environment we have noticed on multiple machines acrodist.exe (Acrobat Distiller) is randomly maxing out 1 CPU core. So on dual-core machine there is 50% utilisation, quad-core 25% utilisation, octa-core 12.5% cpu utilisation.
This is even when the end-user is not using any Acrobat or PDF related applications. Upon investigation using Process Explorer we have noticed approx. 10 minutes after first bootup, for some reason acrotray.exe calls Distiller (acrodist.exe) under the users context using the following command line:
acrodist /N /P --UseSystemFonts /Q:15
The acrodist.exe process then proceeds to run indefinitely maxing out 1 CPU core until it is manually terminated from task manager.
Using help files I know what the switch parameters /N (new instance of Distiller) and /Q:15 (quit after 15 seconds of completion) do but I cant figure out what /P --UseSystemFonts is asking Distiller to do. Anyone got any ideas? Our theory is that is getting stuck trying to process a font but no idea which one. Any help would be much appreciated.
We've tried to analyse the process threads using Process Explorer and Process Monitor but have not been able to get anything useful of what acrodist.exe is actually doing or what it's stuck on.
Confirmed this problem exists on at least 140 of our Win7 SP1 (32 and 64-bit) machines with Acrobat XI (v11), both Standard and Pro versions affected