onnxruntime causing high CPU while typing in Visual Studio 17.8.4

[Shashank231190]

Describe the issue

Whenever I am typing in visual studio version 17.8.4 its starts consuming high CPU.
Is there any way I can stop it ?

Its loaded in process
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\ServiceHub\Hosts\ServiceHub.Host.netfx.x64\ServiceHub.IntellicodeModelService.exe

I have collected the dump by using procdump by using command -

procdump -n 3 -s 2 -c 10 4776

0:007> !runaway
User Mode Time
Thread Time
5:2150 0 days 0:00:19.703
6:858 0 days 0:00:15.015
7:298c 0 days 0:00:14.109

Stack for high CPU.

Call Site

00 ntdll!ZwWaitForAlertByThreadId
01 ntdll!RtlSleepConditionVariableSRW
02 KERNELBASE!SleepConditionVariableSRW
03 onnxruntime!OrtSessionOptionsAppendExecutionProvider_CPU
04 onnxruntime!OrtSessionOptionsAppendExecutionProvider_CPU
05 onnxruntime!OrtSessionOptionsAppendExecutionProvider_CPU
06 ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>
07 kernel32!BaseThreadInitThunk
08 ntdll!RtlUserThreadStart`

To reproduce

1. Start visual studio.
2. Start a new C# project, Console application [.NET Framework]
3. Start typing in visual studio it will automatically start consuming CPU.

Urgency

I am not able to code anything on visual studio

Platform

Windows

OS Version

Windows 10

ONNX Runtime Installation

Released Package

ONNX Runtime Version or Commit ID

1.14.23.224

ONNX Runtime API

C#

Architecture

X64

Execution Provider

Default CPU

Execution Provider Library Version

No response

[Shashank231190]

I disabled features in Intellicode section in visual studio Tools -> options -> Intellicode -> general and it stopped spiking the CPU.
However now, ServiceHub.RoslynCodeAnalysisService.exe has started spiking now.

Followed this link : https://learn.microsoft.com/en-us/visualstudio/ide/visual-studio-performance-tips-and-tricks?view=vs-2022#managed-language-service-roslyn

Found I don't have CodeLens feature enabled.

[github-actions]

This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details.