I usually use only Firefox, but when I need to launch Chrome to test something, this reporter tool creates a very significant load one the system in terms of SSD and CPU usage. For the last few times I have simply killed the process, but will see if any of permanent ways to disable this reporter tool really work.
Deleting it doesn't work since it is recreated on startup of chrome.
I modified the folder acl '\AppData\Local\Google\Chrome\User Data\SwReporter' to not be able to run the executable. That seems to stick (at least when run as a limited user).
Does that also happen if Firefox is closed when you launch Chrome ?
I ask because for a long while I had a bug where launching Chromium while Firefox is running would show similar symptoms, on top of freezing Firefox. This didn't happen if I closed Firefox before launching Chromium.
