Jump to content

ESet high CPU when Visual Studio 2022 starts


Peo
 Share

Recommended Posts

Hi.

Since about a month Eset service will take 90+% cpu as soon as Visual Studio 2022 starts.
This lasts for several minutes and makes it almost impossible to do anything.
Then it is back to normal. It is the same even if VS does not loads a project.
I have made a repair of VS, but no difference.
PC is 8 core 32 GB RAM so that should not be a problem.
/Peo

Link to comment
Share on other sites

Yes, then VS load is quite normal and no extra cpu-load.

If I deactivate during VS load and the activate immediately after that, everything is normal.

Link to comment
Share on other sites

  • Administrators

Please provide a Procmon log from time when the issue is manifesting. It should be enough to leave logging enabled for 2-3 minutes.

Link to comment
Share on other sites

Unfortunatly the zipped log is about 275 MB so I cannot post it here. Can I send it somewhere else?

Link to comment
Share on other sites

  • Administrators

Yes, you can upload it to OneDrive, Dropbox, etc. and drop me a private message with a download link.

Link to comment
Share on other sites

  • Administrators

How much does adding the folder C:\Temp\Default\ServiceHub.Host.CLR.x86.exe\*.* to performance exclusions improve the situation? If not much, what about adding C:\Temp\Default\*.* ?

Link to comment
Share on other sites

The first was no notable difference but with the second it was much better.

Link to comment
Share on other sites

  • Administrators

The problem is that ~34,500 html files were created which were subsequently scanned. This had adverse effect on performance. Instead of the performance exclusion above, please exclude the processes (with full path):

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\devenv.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.AnyCPU\ServiceHub.Host.CLR.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.x86\ServiceHub.Host.CLR.x86.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.x86\ServiceHub.IdentityHost.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.x86\ServiceHub.SettingsHost.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.x86\ServiceHub.ThreadedWaitDialog.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.AnyCPU\ServiceHub.RoslynCodeAnalysisService.exe

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\ServiceHub\Hosts\ServiceHub.Host.CLR.AnyCPU\ServiceHub.VSDetouredHost.exe

 

Link to comment
Share on other sites

Thank you for pointing this out. To start I just deleted everything in the Temp folder and all is back to  normal. If it doesn't stay so I will exclude the processes according to your advice.

Link to comment
Share on other sites

  • 1 month later...

I have a user who has the same issue, temporarily excluding the entire temp folder and entire VS directory made no difference. Nor did deleting the temp folder contents. I have asked the user to create a procmon log and will open a case and if a solution is found, will update here too with any solutions. Be interested to see if this is a common issue with VS 22. 

Link to comment
Share on other sites

  • Administrators
17 hours ago, IT-Ryan said:

I have a user who has the same issue, temporarily excluding the entire temp folder and entire VS directory made no difference. Nor did deleting the temp folder contents. I have asked the user to create a procmon log and will open a case and if a solution is found, will update here too with any solutions. Be interested to see if this is a common issue with VS 22. 

Please carry on as follows:
- in the advanced HIPS temporarily disable Protected service and reboot the machine
- start logging with Procmon
- reproduce the issue
- stop logging
- re-enable Protected service and reboot the machine
- provide me with:
1, the Procmon log in a compressed form
2, logs collected with ESET Log Collector.

Link to comment
Share on other sites

Hello. In my case it was the FusionLogViewer that caused filling up the temp folder with thousands of files.

Run fuslogvw.exe from an elevated prompt and disable logging (or select the level you want)

Forgot to mention the solution here earlier, sorry about that.

Fusion Log Viewer settings

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...