Not sure what the latest version introduced, but I have some large unit test files (40k lines) that have become unusable with CRR 16.2.5. I can't even type comments without 10-15 seconds between letters appearing on my screen. Without doing anything productive and only having the file open and clicking around inside of VS has my process steadily using 35% of my processor and memory usage spikes to 2gb where previously it would be around 1.1gb.
When I roll back to 16.2.4 and turn off auto-updating then speed is good. I want to upgrade to 16.2.5 because it resolves obnoxious issues with the DeclareProvider and doing any kind of real work. (I end up turning that off, but then my frequently used quick actions don't get sorted to the top.)
Is there something I can do to help diagnose the speed hit? It's instant and very noticeable. It only seems to happen in large files, though. Standard code files seem okay so far.
Hi Jason,
I have managed to reproduce the issue. Please give us some time to research the issue in detail.