Search and replace bug

[BerendKemper]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.91.1
• OS Version: Windows_NT x64 10.0.19045

Steps to Reproduce:

1. Use the global Search feature in order to find certain string occurences in your repository (in my case up: `out`)
2. For 70 files inside the repository replace the matching string occurence with another string (in my case op: `in`).
3. It can turn out that a few of these files are incorrectly handled by the global search and replace feature.

Proof below in the form of screenshots:

[BerendKemper]

My colleague tells me he experiences the same issue occasionally.

[andreamah]

Hmm.. that's strange. when it first matches, does it match the correct ranges? Do you have a repo that I could test with?

[BerendKemper]

Please give me some time to provide an example repository. The repository where it is taking place is not public and owned by my employer. I cannot share the repository from my employer. Can provide a repository over the weekend.

[BerendKemper]

I am adding some screenshots from git differences in order to help this ticket and or ticket 223289.

74 files were changed during a single search and replace action. Amongst these 74 files:

• 6 files were corrupted and had two instances of keywords that were meant to be replaced.
• 27 files were not corrupted and had two instances of keywords that were replaced.
• 41 files were not corrupted and had one instance of keywords that were replaced.

6 corrupted files - 2 instances keywords:

27 not corrupted files - 2 instances keywords:

41 not corrupted files - 1 instance keyword:

[andreamah]

That's really strange. In the issue you linked, it was a different issue because the corrupted lines were the ones that had multiple matches in one line. However, it seems like there's no matches that were meant to be on the same line. Do you have a repo that I can clone to try to reproduce this?