- This topic has 15 replies, 5 voices, and was last updated 5 years, 7 months ago by
.
-
Posts
-
As long as the system doesn’t lose calibration, there should be no ill effects of processes triggering a reload. On my system, there are two dllhost.exe instances (COM targets “WebPlatformStorageServer” and “Thumbnail Cache Class for Out of Proc Server”, which typically run in the background permanently).
I can imagine Windows 10 dynamically kicking off routines with dllhost.exe in the background for regular Windows operation.
Yes, I don’t think there’s reason for concern.
Also, I’m thinking the sandboxed process model of Chrome makes those processes come and go like crazy.
Indeed. Even just navigating and not opening any new tabs makes chrome put every domain into its own sandboxed process. It’s a quite good security model and allows for easy parallelization.
