Wrong completion matches temporarily

[Peter-Juhasz]

Version: 17.9.0 P2.1

For the request p, the wrong completion (AbandonedMutexException) is selected temporarily instead of the obvious one (p lambda expression parameter). After a short time, the right one gets selected, but you can see on the video that the wrong completion is temporarily gets selected:

Rogzites.2024-01-10.132539.mp4

This can be frustrating when I just type continuously (in this case p) and get a random completion activated (on ) because a wrong completion was selected):

Rogzites.2024-01-10.133014.mp4

May be related to #9724 #9725 in terms of there are obviously timing issues somewhere in the system.

[Peter-Juhasz]

This is a shorter repro, o matches #region first and then object:

Rogzites.2024-01-10.134038.mp4

[Peter-Juhasz]

This is another case when I try to type out and get AccountLayout committed by a random completion:

Rogzites.2024-01-14.135316.mp4

It feels like (in same cases) selecting completions are late by at least a few hundred milliseconds for each character. May not be clearly visible on this recording, but I can see the selection jumping in the completion session as I type character by character. Unless I type like super slow (and wait for the right completion to be matched), I get a random completion activated, which is quite frustrating.

[Dean-NC]

The issue of typing a HTML tag or attribute fast, and pressing tab to accept the 1st intellisense item, and getting the wrong tag put in happens regularly for me in .cshtml files. It's so annoying. After it happens, most of the time it won't repeat the problem for that same tag at that same editor location, meaning it works after erasing it and re-typing/tabbing. But sometimes after it happens and I erase and slowly re-do it, I can see that intellisense doesn't have that item in the list, and I have to type the full thing without being able to press tab.