Multi-file find and replace spawns multiple processes per file

[wbrefvem]

Steps to Reproduce:

1. Search workspace for a common string.
2. Replace it with any other string.

Results:

1. System resource usage should spike
2. Process table should reveal a large number of go-related processes (gofmt, golint, goreturns, etc).
3. Processes do not appear to be children of any VS Code process, so they persist even after exiting VS Code.

[ramya-rao-a]

Looks like the save at the end of replacing is triggering all the on save related features like formatting and linting

[ramya-rao-a]

This can be fixed by ensuring that we only run the build/lint/vet/format actions on an active document instead of each of the saved document.

I have pushed a commit for the same, thanks for reporting!

[ramya-rao-a]

The fix for this is now out in the latest update (0.9.0) to the Go extension