Closed gbockus-sf closed 2 months ago
This turned out to be associated with the inlineSuggestDelay advanced setting that allows the user to add buffer time before processing IAC requests. The default is 250 ms. If this value is too large then we see a bunch of async calls piling up waiting which impact cpu/memory on the system.
Thanks again for your help with this!
Summary
When IAC is enabled in E4D sometimes you will encounter a situation where the inline provider appears to get stuck in a trigger loop resulting in it consuming the CPU resource and causing VSCode to be sluggish.
The current guess is this is somehow related to the Apex prettier extension and some interaction between the two extensions. The case reported where it comes up most often is when formatting a file with apex prettier E4D will start to consume the CPU and has to be disabled to allow the file formatting to complete.
Steps To Reproduce:
Reported on a high end windows machine, but has also been seen by other member of the team across OS's.
Expected result
E4D should not lock up VSCode
Actual result
CPU is consumed with canceled IAC requests.
Additional information
User @jamessimone salesforce extension pack: 60.11.0 einstein for developers just updated to 0.45.1 this morning Windows 11 Enterprise 22H2 VS Code version: 1.88.1