I have this issue. If I access image or video files Windows doesn't "like", DLLHOST.EXE will fire up and chew about 40MB of memory every 2-3 seconds. I noticed it after it ate 8GB of RAM and the system almost died.
Now...I just kill it. I then also kill the process tree that spawned it. This usually stops it from appearing until some other app calls it or I close / re-open the app I'm using.
As far as i can tell killing it doesn't hurt anything at all - with the apps I'm using (mainly Chrome and Magix Movie Pro 2013 Plus). I mainly use Linux.....but the video editing app I prefer runs on Windows, so I have a Windows system to run it on.
It may be that I have installed a buggy video or audio codec along the way somewhere.......that I needed to be able to process my video at all.....soif I have to choose between the (unknown, possible) video codec and killing DLLHOST.EXE.....then I'll be digging a grave for the pain in the a*se DLL every single time.
If it should prove to be that I do need the DLL running fomr some specific purpose or service I can't otherwise perform....then I'll leave DLLHOST.EXE running until that purpose has been served...and then kill it.
My system did not used to behave this way......but it started not long after Windows 8 came out. Maybe it's just Microsoft trying to give me a reason to downgrade to Windows 8. I don't know.
Edited by Linuxluver, 10 September 2013 - 04:43 PM.