Bug: Files randomly starts using as much CPU usage as possible

[Josh65-2201]

Description

After 3.7, Files randomly will use as much CPU as possible after navigating folders with no consistent way of triggering it. I have calculate folders sizes and leave running in the background turned off and I'm not running any file operations during or before this happens.

Steps To Reproduce

Unknown

Requirements

Unknown

Files Version

3.7.6.0

Windows Version

10.0.22631.4169

Log File

debug.log

[yaira2]

I haven't noticed any issues on my side but I haven't had any long sessions lately. Do you know around which preview build this started happening? Are you able to check earlier commits in main to try and figure out at which point it started occurring?

[Josh65-2201]

3.7.4 is the earliest I noticed it. I can try the commit but since it kind of random it could take a while

[yaira2]

Having a more specific commit would help debug, but either way I'm not sure how much I can do unless I can repro it as well 🙁

[yaira2]

@0x5bfa I think this might be the update where we removed WinUIEx.

[0x5bfa]

@Josh65-2201 what if you open a property window, close the main window and move your cursor? If the same happens, it might be caused by my commit.

[Josh65-2201]

Doing that does have a noticeable 0.1% when not moving the cursor to about 25-30% when moving it. Even just opening preview though has it siting at 38-45% after Files has loaded for a while before going down to 0.1% as expected

[0x5bfa]

Do you mean preview is preview pane?
Consuming CPU just moving cursor is silly. If you pointer out of the widow does it fall down?

[Josh65-2201]

No, Files preview. With Files freshly open only moving the cursor around is causing high CPU usage, I haven't had Files start using as much as possible yet, but can try moving the cursor out the window when it happens

[yaira2]

Can you repro with #16100?

[Josh65-2201]

Moving the mouse out or minimizing the window doesn't lower CPU usage after it happens. Is #16100 based on 3.6.18? If so probably not since 3.7 doesn't have the issue

[yaira2]

Should be based on a commit with WinUIEx, but we've tested with a lot of branches and it's possible there are other changes as well.

[yaira2]

What about #16138?

[Josh65-2201]

I will build on that commit and try it for a few days see if it happens