Memory Leak with new Hyperion 2.1.1 on Windows 11

[mikifriki]

• I confirm that this is an issue rather than a question.

Bug report

Since I have Hyperion set to launch on windows startup then it slowly starts using up more and more RAM until It almost runs out. I found this out since I saw that my pc became unresponsive even when on desktop. Once I viewed the Task Manager I saw that Hyperion was using 20Gb of memory and kept going. Added my current configuration and log output which I got during the issue.

HyperionBackup-2025-07-09_v2.1.1.json

Log Output.txt

Steps to reproduce

Note: This does not happen always on startup but i frequently encounter it during this time.

1. Install latest hyperion windows.
2. Setup Hyperion with two instances
3. Restart windows and see how keeps using more and more memory.

What is expected?

Hyperion keeps using the same amount of ram on a blank black screen desktop

What is actually happening?

Hyperion keeps on using more and more ram.

System

Hyperion Server:

• Build: LordGrey-bde49a8/26fd6d8-1749918223
• Build time: Jun 14 2025 16:50:08
• Build type: Release
• Git Remote: https://github.com/hyperion-project/hyperion.ng
• Version: 2.1.1
• UI Lang: en (BrowserLang: en-GB)
• UI Access: advanced
• Avail Screen Cap.: qt,dda
• Avail Video Cap.: v4l2
• Avail Audio Cap.: audio
• Avail Services: boblight,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection
• Config database: C:/Users/mihke/.hyperion/db/hyperion.db
• Database: read/write
• Mode: GUI

Hyperion Server OS:

• Distribution: Windows 11 Version 24H2
• Architecture: x86_64
• Kernel: winnt (10.0.26100 (WS: 64))
• Root/Admin: false
• Qt Version: 6.8.3
• Python Version: 3.13.3
• Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Edg/138.0.0.0

[Lord-Grey]

Thanks for sharing your finding.
Could you test with the latest build from PR #1884, please.
Note: Do a configuration backup before.

https://github.com/hyperion-project/hyperion.ng/actions/runs/16153477417

I assume the memory consumption is related to issue #1882

[mikifriki]

Hello! Thanks for the fast response.

I tested this version I still run into the same issue. However I was able to find a stable way to recreate the bug.

1. Start Hyperion
2. Go to Settings -> General
3. Disable or Enable a LED Hardware instance (either way works)

After this ram keeps getting allocated without stopping. With these steps I was also able to recreate this issue on MacOs 15.5 so it should not only be OS specific.

On MacOs I tested with 2.1.1 and the new build provided in your comment. (added MacOs System also below the same way as in the template)

System

Hyperion Server:

• Build: LordGrey-bde49a8/26fd6d8-1749918223
• Build time: Jun 14 2025 16:47:54
• Build type: Release
• Git Remote: https://github.com/hyperion-project/hyperion.ng
• Version: 2.1.1
• UI Lang: en (BrowserLang: en-US)
• UI Access: default
• Avail Screen Cap.: osx,qt
• Avail Video Cap.:
• Avail Audio Cap.:
• Avail Services: boblight,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection
• Config database: /Users/Xerxes/.hyperion/db/hyperion.db
• Database: read/write
• Mode: GUI

Hyperion Server OS:

• Distribution: macOS Sequoia (15.5)
• Architecture: arm64
• Kernel: darwin (24.5.0 (WS: 64))
• Root/Admin: false
• Qt Version: 6.9.0
• Python Version: 3.13.4
• Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.5 Safari/605.1.15

[mikifriki]

Hey again! A small update on the issue. I tested this on a different Mac and on the same Windows again to try and see if any specific configuration causes this and I found the following.

Seems like the memory consumption issue only appears if a LED instance which has screen capture enabled, gets stopped/started from the general view. On mac I tested with the OSX/QT grabber and on windows I tested with QT.

Without any screen capture on an instance there is no memory consumption issue when it is started or stopped. Next up I will try to see what could be causing this issue in general