system-bridge icon indicating copy to clipboard operation
system-bridge copied to clipboard
verified publisher icon timmo001

Memory leak, systembridgebackend.exe

Open kariudo opened this issue 1 year ago • 3 comments

Description

It would appear that after every invocation of the SystemBridgeWindowsSensors.exe the systembridgebackend.exe is leaking memory. It is not a hufe amount (20-30k) but over days it adds up and seems to create a noticable impact on performance (possibly in the form of stuttering on intervals).

The aforementioned stuttering goes away when closing and relaunching System Bridge.

I have not run a memory dump/trace on it, but just observed the slowly increasing memory allocation.

What Platform / OS are you running?

Windows

What version are you running?

4.1.10

Anything in the logs or a references that might be useful?

No response

Additional information

No response

kariudo avatar May 21 '24 13:05 kariudo

Hi, noticed the same, usually after letting my computer sleep or that maybe just that it's running longer so has more time to leak. It's immediately noticeable by the heavy stuttering, even while just on the desktop with nothing else running. Killing/Restarting System Bridge solves it.

boroborob avatar May 25 '24 18:05 boroborob

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

github-actions[bot] avatar Jun 25 '24 08:06 github-actions[bot]

This is very much still a problem. There has been no change.

kariudo avatar Jun 25 '24 12:06 kariudo

I installed it on my NAS which is running 24/7. After a while I noticed that there are around 20 processes of systembridgebackend and they took about 2 GB of RAM. After a restart of systembridge there are only 7 of the processes left and the RAM usage went down to 200 MB.

Update (2025-05-07): After 2 days the memory went to up ~700 MB

jd1 avatar May 05 '25 09:05 jd1

This issue has been marked as "legacy" because it pertains to a version of the application that is being replaced.

For more information on the application rebuild, please see the main tracking issue: #3392 and the project README.

Once the new version is released, this issue will be re-evaluated. Thank you for your patience.

github-actions[bot] avatar Jul 29 '25 16:07 github-actions[bot]

This issue was marked as legacy. Since 5.0.0 has been released, I will close this issue. If you are experiencing this issue in the new version, please open a new issue. Thanks

timmo001 avatar Aug 23 '25 13:08 timmo001