So, every once in a while, I get a dllhost.exe that runs away. My solution is, after it consumes enough memory to take down HS or whatever other service that gets killed off...I go downstairs, kill off that dllhost.exe and then restart the PC to get all the services back up and running.
So, I thought, why not put a script together to monitor this dllhost.exe and kill it, if it ever gets above say 256MB.
So, I poked around the internet, found this:
http://www.neowin.net/forum/topic/61...-memory-usage/
I initially forgot, that in settings.ini, I had to add in System.Diagnostics and System.ComponentModel to scripting references. So, I did. Shutdown HS, brought it back up.
When I run the code that is in that link, I get this error message in the log:
Script compile error: Type 'Process' is not defined.on line 440, which is the debug line for where I put the Dim processes()
Poking around more on the internet, I found this:
http://msdn.microsoft.com/en-us/libr...v=vs.110).aspx
Which seems to validate that process is actually part of System.Diagnostics.
Later on in the code, there is a collection (?) that is used, so I am guessing that is why System.ComponentModel is being included.
Any help is appeciated...or if you know of another way to go about this, I'm all "ears" !
--Dan
So, I thought, why not put a script together to monitor this dllhost.exe and kill it, if it ever gets above say 256MB.
So, I poked around the internet, found this:
http://www.neowin.net/forum/topic/61...-memory-usage/
I initially forgot, that in settings.ini, I had to add in System.Diagnostics and System.ComponentModel to scripting references. So, I did. Shutdown HS, brought it back up.
When I run the code that is in that link, I get this error message in the log:
Script compile error: Type 'Process' is not defined.on line 440, which is the debug line for where I put the Dim processes()
Poking around more on the internet, I found this:
http://msdn.microsoft.com/en-us/libr...v=vs.110).aspx
Which seems to validate that process is actually part of System.Diagnostics.
Later on in the code, there is a collection (?) that is used, so I am guessing that is why System.ComponentModel is being included.
Any help is appeciated...or if you know of another way to go about this, I'm all "ears" !
--Dan
Comment