Memory leak

[cdmn1]

App running for a few days develops a terrible memory leak

[Desmond-Dong]

I’ve pushed an update. Hopefully this improves it.

[cdmn1]

Ok, I will test the new version and will report back in a few days.

[cdmn1]

Memory leak still present.

This updated client was started minutes after my previous post 4 days ago.

[Desmond-Dong]

I dug into this again and pushed a more targeted set of fixes to .

The most likely long-running growth was in the Windows audio playback path, especially when remote audio/TTS was played repeatedly without VLC available. That path has now been changed to use temp-file backed playback instead of loading full remote audio responses into memory.

I also added:

• a hard limit for the ESPHome protocol receive buffer
• safer hotkey cleanup to avoid leftover listener threads
• a cap for the single log file size

So this is no longer just a generic 'hopefully improved' update - there are now concrete fixes for the most likely memory growth sources.

There is also one more stability fix on : the app now stores a persistent device identity instead of relying on the runtime MAC from the current environment.

Please test again with the next release when it is published. If memory still grows after that, the next place I would investigate is native memory usage inside the wake word/audio stack rather than Python object growth alone.

[Desmond-Dong]

Correction: all of the fixes mentioned above have already been pushed to main.

[cdmn1]

The issue remained with 0.4.6

Just started a fresh instance of 0.4.8. 70.3mb memory footprint on launch.
Will report back in a few days.

[cdmn1]

memory leak still present with 0.4.8

[Desmond-Dong]

To help me better diagnose the issue, could you please provide the following information:

1. Whether VLC is installed on your system
2. Approximately how many voice messages are played per day
3. Whether you are using the Home Assistant app to play audio/music
4. Any available logs from your system

You can find the logs at:
C:\Users\<your_username>\AppData\Local\HomeAssistantWindows

If you can also describe the specific situation or steps that trigger the issue, that would be even more helpful.

Thank you for your support — this information will help us identify the root cause more efficiently.

the latest version also can diagnose the issue in ESPHome

[cdmn1]

• Whether VLC is installed on your system
  Yes
• Approximately how many voice messages are played per day
  None
• Whether you are using the Home Assistant app to play audio/music
  No
• Any available logs from your system

ha_windows.log

Immediately after my last post I updated to 0.5.1, it uses around 60/70mb after starting, today it shows over 2GB again.

This is used in an always-on computer. I'm am only using the app for the sensors so it stays idle/in the background, I am not using media playback or voice satellite features.

[cdmn1]

Just started a fresh instance of 0.5.2 with 70.1mb memory footprint on launch.
Will report back in a few days.