Memory leak?

[kt767]

I have Homebridge 1.5.0 (Node.js v16.16.0) installed on Raspberry Pi 4 (2GB RAM) that is running OpenMediaVault 6. I installed the Tesla Powerwall plugin as a separate bridge this morning, and I can see "home bridge: homebridge-tesla-powerwall" gradually using more and more memory when I run htop (VIRT column goes up consistently). Is anyone else having the same issue? Here's a graph from OMV's GUI:

I tried v3.1.0-Beta5, but VIRT memory consistently increases, just like v3.0.0.

Here is my config:

        {
            "platform": "TeslaPowerwall",
            "name": "Tesla Powerwall",
            "_bridge": {
                "username": "1E:82:FA:2C:5F:1F",
                "port": 56251
            },
            "ip": "192.168.82.23",
            "password": "[redacted]",
            "additionalServices": {
                "powerwall": {
                    "eveHistory": false
                },
                "solar": {
                    "homekitVisual": false,
                    "evePowerMeter": false,
                    "eveHistory": false
                },
                "grid": {
                    "positiveEvePowerMeter": false,
                    "negativeEvePowerMeter": false,
                    "eveHistory": false
                },
                "battery": {
                    "positiveEvePowerMeter": false,
                    "negativeEvePowerMeter": false,
                    "eveHistory": false
                },
                "home": {
                    "evePowerMeter": false,
                    "eveHistory": false
                }
            }
        },

[datMaffin]

Any long term experience? Did the usage level off at some point?

[kt767]

I didn't notice the usage leveling off after a few days, so I ended up uninstalling it.

[longzheng]

I've also experienced this since installing this plugin. I haven't had much time to debug it further but restarting it recovered about 3GB for me after 3 days of usage.

[datMaffin]

As long as only the virtual memory increases, it should not be a problem. (Linux can basically provide an infinite amount of virtual memory).

I do not like that it seems to be triggered by this plugin, though: Are other Homebridge plugins fine?
I will check if I can see similar behavior, but the memory usage seems to at least only increase very slowly (if at all).

Is there anyone that is more familiar with the Node ecosystem and is able to provide a pointer to how best to debug this?
Or is this common behavior of Node that should be fine?

[azurecrash]

Can confirm I am having the same issue here on the latest version of Homebridge and this plugin. Homebridge consumes approx 1GB of additional memory per day until the system becomes completely unresponsive and is physically restarted. Unsure of which plugin was the culprit, I was able to identify this one by process of elimination. Subsequently, we can see memory consumption is way more under control.

After the vertical blue line at right - which is where I disabled the plugin - the rate of mem consumption (slope of the light blue line) flattens. Prior, you can see several runs up and fall offs. The fall offs are reboots and service restarts, but the consumption of memory is at a standard rate.

Hope this helps

[prwhite]

Having the same issue. Just upgraded HomeBridge from older version to v1.7.0 including going to node 18.19.0 from 16.x. The homebridge process (not running any child bridges) grows for a couple of days and then I need to restart the process or else the system gets deeply into swap and ultimately becomes unresponsive. My setup was far more stable before these upgrades.

I attached Chrome dev tools to HomeBrige with NODE_OPTIONS --inspect.... After taking a couple heap snapshots 10 minutes apart, an overwhelming majority of the top "# Delta" and "Size Delta" entries appear to be related to this plugin. I attached some images of representative output from the dev tools session below. I can provide more info if it will help.

Of course, I changed more than one thing around the time of this version upgrade. I started sending MQTT messages to some clients when I get these PowerWall events. I suppose it's conceivable that through that new part of the flow something is getting unintentionally retained, although it's really straightforward stuff. I'm going to do some experiments to see if I can disable that part of my setup and see if there's a difference in memory behavior.