Besides, what you'd like to know is probably not how many megabytes TinyWall uses, but whether it will slow down your computer. ![]() Most PID's for svchost are associated with multiple services though so this method isn't perfect. The end effect of all these is that the actually used amount of memory is less than what is reported to you by such simple tools. Try Binisoft's Windows Firewall Control v4 which would show you which process ID the blocked connections from svchost.exe is from, then cross reference the PID with Process Hacker or Process Explorer to verify which service is causing the connect outs. The two processes of TinyWall share a lot of things in memory which are thus loaded only once, but Windows counts them separtately for each process, thereby double-counting a significant portion of TinyWall's memory usage. Third, you'd be mistaken to sum the memory used by the two TinyWall processes. ![]() Net runtime, which is higher but not really all used. Second, what the Task Manager counts is not the memory reserved by TinyWall itself, but the memory reserved by the. This is how Microsoft designed it, and it happens with all. Net processes have a somewhat increased memory usage, because of the supporting runtime that gets loaded, but this is perfectly normal and expected. Net processes like TinyWall, is more complicated than looking at the values reported by the Task Manager. ![]() Memory analysis of a process, especially of. Why does TinyWall seem to use a lot of memory?
0 Comments
Leave a Reply. |