SmartConsole login-window causing high CPU

[Mikael]

Hello,

Has anyone else noticed if SmartConsole causes high CPU-load when left at the login-window?

On my machine, all clients after R80.30 (R80.40, R81 and R81.10 EA) use around 40% CPU just showing the login-window.

Not that this is a major thing but sometimes the client is either disconnected due to the session-timeout or I open the client but something distracts me and I won't login for a little while...

I normally realise this has happened when the fans of my laptop go crazy.

This is a Win10 VM with 4 cores and 8 GB of RAM.

Cheers

[G_W_Albrecht]

No, not at all:

But this is no VM. GPU is rather high, though...

[Timothy_Hall]

While the CPU usage isn't as high on my system when the SmartConsole is left at the login window, it does seem to persistently sit at about 5% for me.  Windows Process Explorer reveals that the SmartConsole.exe thread consuming the CPU is "wpfgfx_v0400.dll!MilVersionCheck".  This appears to be a component of the Windows Presentation Foundation which is part of .NET.  So it doesn't seem to be something in the SmartConsole executable itself but the underlying .NET framework.

If you download Windows Process Explorer can you confirm that you see the same thread?

[Mikael]

Yes that's one of the threads that seem to cause the issue.

This is what it looks like when I leave the R80.40 console without loging in...

I wonder what changed between R80.30 and R80.40 since it doesn't happen with the R80.30 SmartConsole...

[CPIshai]

Hi @Mikael, 

Can you please share with me your SmartConsole Version? I would like to check it as well.

Thanks,
Ishai 

[Mikael]

Hi,

R80.30 that doesn't have this issue and works as expected is build 993000099

R80.40 with the issue is build 994000414

R81 with the issue is build 995000549

R81.10 with the issue is build 81.10.9600.306 (ran out of demo instances to connect to to get the build-no. so this is what's displayed in the login-window)

They are all running in the same Windows 10 VM.

Windows 10 Pro, 21H1 (build 19043.985) with all available patches applied.

The latest .Net Framework cumulative update for 21H1 has been applied.

4 cores and 8 GB of RAM

[G_W_Albrecht]

What is the Win10 VM running on ?

[Mikael]

It's running on a 2018 Macbook Pro, 6-core i7 with 32GB of RAM.

[G_W_Albrecht]

I see... So it is incomparable to a true Win10 installation ! As long as it is not too troublesome i would just bear it as it is 8)

[Mikael]

Sure, it's not that big of a thing. Was just looking to see if this was a general issue as I believe I have seen it in other environments as well. 🙂

[Henrik_Noerr1]

We spend many days debugging a similar issue, we have several toolstations with many connected admins to our MDS Domains.

All toolstations were 100% loaded. Evetually we found out that when some admin had a gateway open, normal/cluster/VS - SMC used one core 100%. This all added up to unusable toolstations for all.

Solution was to run SMC in Windows 7 Compatibility mode.

We are using Windows Server 2016 for OS on toolstations.

/Henrik  

[Mikael]

I gave this a try but couldn't see any difference in the behaviour on my machine.

Good idea though!

[CPIshai]

I want to thank @Mikael  for his time, with his assistance we believe that we found the reason why in some environments the CPU (or GPU) rises up on the login view. 

We are working on it.

Thanks,
Ishai