Total Commander uses full processor

[Laszlo]

After a while, Total Commander uses the full processor power. I've got a 4 core setup, so it's 25% constantly. It happens when total commander is in the background, doing nothing. I usually start total commander when I turn on PC, and never quit. It didn't occur in the 8.50 series, but appeared in the 9.0 series. The strange thing is that I cannot tell you when is this, like, after 1 hour idle, or 2, or just 10 minutes, it just happens. I've got 2 PCs, and this bug appeared on both of them.

[ghisler(Author)]

I need more information. Please do the following:

1. Update to TC9 RC6.

2. Please add the following (undocumented) string to the file wincmd.ini, section [Configuration]:
DebugThreads=1

You can edit the wincmd.ini via Configuration - Change settings files directly.
This will create a tcthreads.txt in TEMP directory, which shows which thread name has which thread ID.

3. Restart Total Commander

4. Get the program "process explorer" from www.sysinternals.com

5. When the error occurs, run process explorer and double click on the totalcmd.exe or totalcmd64.exe

6. Check the ID of the thread with 25% CPU.

7. Look up the thread name in tcthreads.txt

Please also send me a stack of the busy thread (also from process explorer).

[Laszlo]

Here you go:

https://www.dropbox.com/sh/38f9ep4z7v362yk/AABIAIpJekAbpJFH3mctcOrxa

What I realized is that when I noticed the 25% CPU use in the background, and I clicked on the total commander windows taskbar (so now it is showing in the foreground) the CPU use went down to 0%. So maybe it is a minimize bug.

[ghisler(Author)]

Thanks, that helped. The problem is caused by auto-refresh option set to "Don't react to updates while in the background".

It should go away when you disable this option. I will fix it in the next version.

[Laszlo]

I see thanks!

[Hurdet]

Do it is normal that tc when not inactive execute TWatchDirThread and TCheckDirThread thread if i have disabled any auto-refresh?
I see that now as TC has no more the old problem TC use 0.11% cpu constant.

[ghisler(Author)]

Yes, it's normal, they are also used for other things like watching drive icon changes. But they should consume almost no CPU now.

[Hurdet]

I confirm: they consume almost no CPU now. Ty.

[dobandvla]

TC ver 9.51 ignores maximum processor state (set to 10%) in windows 10 ver 2004 (when brings to front - always uses 100%)

[Horst.Epp]

Why should TC honor such a setting ?
Its not under control of TC, so blam Windows power management.

[MVV]

Well, I agree with Horst.Epp that such Windows feature must be controlled by Windows only, not applications. I don't even know how an application can control processor speed, and I believe it shouldn't because it knows nothing about other applications and their activities.

[dobandvla]

TC ver 9.51 ignores maximum processor state (set to 10%) in windows 10 ver 2004 (when brings to front - always uses 100%)

Sorry for long delay (completely forgot about this post ;-( ), but, answering that:

Why should TC honor such a setting ?
Its not under control of TC, so blam Windows power management.

I see misunderstanding or/and lack of knowledge here.

Windows maximum processor state limits maximum processor frequency systemwide AFAIK (and mandatory for all apps), and I don't know exception to this rule.

When windows doing nothing (cpu utilization is 1-2%) and TC brings to front (doing nothing too), windows always switches to
100% frequency disregarding maximum processor setting (and cpu utilization is still 1-2%).

PS just noticed (windows 10 21H2), maximum processor state now limits cpu utilization instead of frequency (when this happen I don't know). What a creepy this windows 10 thing!