Bug: Excessive Memory Usage

[ArtanisHong]

Description

After running the FILES App for an extended period, its memory usage continuously increases and eventually reaches several gigabytes (as observed in Windows Task Manager). Additionally, CPU usage spikes dramatically during the following operations:

1. Opening a new tab.
2. Navigating to the parent directory ("Back") in any existing tab.

Steps To Reproduce

1. Launch the FILES App.
2. Let it run continuously (duration may vary, but memory will eventually accumulate significantly).
3. Observe the FILES.exe process in Windows Task Manager:

• Memory usage (Private Working Set or Working Set) shows consumption reaching several GB.

4. Perform either operation while monitoring CPU usage:

• Action A: Click the "New Tab" button (or use shortcut e.g., Ctrl+T).
• Action B: Click the "Up/Back" button (or use shortcut e.g., Backspace) in any file browser tab.

5. During Action A or B, the CPU usage of FILES.exe will spike drastically (e.g., rapidly jumps to high percentages).

Files Version

3.9.1.0

Windows Version

10.0.19045.6093

User ID

32ef2c08-7c4d-49d1-bdaf-ab4af9c33c4c

Log File

debug.log

[yaira2]

Thank you for your feedback, high resource usage & memory leaks are known issues with WinAppSdk. We're somewhat limited with what we can do in this area (implementing Native AOT should help), but we'll keep working on improvements (please see #4180).

A potential workaround is to turn off the option to keep Files running in the background.