BackupSystemTray.exe uses 50+ GB virtual memory, low-memory hangs (5.9.2.1)

[gmygmy]

Hello,

Hasleo Backup Suite 5.9.2.1 on Windows 11 Pro 25H2 (build 26200), i3-12100F, 16 GB RAM, a page file giving a ~29 GB commit limit. A daily incremental system backup (C: + EFI + recovery) goes to an SMB share; the PC sleeps between runs and wakes on Hasleo's wake timer.

Twice, Windows' Resource-Exhaustion-Detector (System log, event 2004, "Windows successfully diagnosed a low virtual memory condition") named BackupSystemTray.exe as by far the largest consumer:

• 2026-09-21 13:08 -> 13:18 (3 events): BackupSystemTray.exe consumed 54.7 -> 58.0 GB; next largest steamwebhelper.exe ~0.45 GB
  
• 2026-10-17 20:59 -> 21:15 (4 events): BackupSystemTray.exe consumed 52.5 -> 57.9 GB; next largest explorer.exe ~0.6 GB
  

The figure kept rising between consecutive events (~1.5 GB per 5 min), and the same PID was named each time, so it is one process growing, not repeated launches. On 09-21 the machine crashed about two hours later.

Separately, on 10-23 and 10-25 the machine hung hard (desktop frozen, mouse dead; only the power button helped). For hours beforehand, Windows could no longer start services (appxsvc and others timing out at 30 s), and BackupWorker was never launched for the 18:05 scheduled backups on 10-23 and 10-24. No event 2004 was logged in that span, so I can't prove the tray app was the cause those times.

After a reboot the tray app sits at ~22 MB private and stays flat for minutes, so the growth is triggered by something later - possibly a sleep/resume cycle or a scheduled backup run.

Questions:

1. Is a BackupSystemTray.exe memory leak known, and is it fixed after 5.9.2.1 (5.9.2.4 is current)?
   
2. Does the tray app need to run at all for scheduled backups, i.e. can it safely be disabled from starting at logon?
   

I can provide the BackupService / BackupWorker logs and the full event-log entries.

[al3x]

Hi and welcome to the Hasleo forums!

I've not seen anyone report any memory leaks for the BackupSystemTray process in this forum so far. I think this is something Hasleo might have to look at.

So yes, attaching all log files from HBS most definitely will help with the analysis.
You can export the full log with the "save log file" action from within HBS:

Please click "" > "Save log file" to open the save log file dialog, save the zip file and attach it to your post.



Hasleo is very active in this forum and you'll probably get a response pretty soon from @admin.

To your other questions:

>> Is a BackupSystemTray.exe memory leak known, and is it fixed after 5.9.2.1 (5.9.2.4 is current)?
I can't tell for sure if this is something that was fixed in a later version, but the changelog doesn't say anything about a memory leak. In general it's a good idea to always run the latest version available, so yes, you should try updating to v5.9.2.4 first. You could also try the newest beta version v6.0.1.0, which is pretty stable already. I use it on a daily basis with zero issues so far.

>> Does the tray app need to run at all for scheduled backups, i.e. can it safely be disabled from starting at logon?
I think this process is started automatically when the "Hasleo Backup Suite Service" is run, so this might be tricky and I don't recommend blocking that process.

Cheers,
al3x