Agent using 20GB+ RAM
Unfortunately I had to close it as I was running out of RAM, and I'm not sure what happened. I went to the store, my monitors went to sleep, and when I came back I found discord and other stuff frozen or crashed, + hass agent using 20 somethingGB RAM
Where should I look for logs or anything that can help us figure out what went wrong? I haven't re-opened it yet just in case that might overwrite some logs or something
40 Replies
Help us Help Others!
To help others find answers, you can mark your question as solved via
Right click solution message -> Apps -> ā
Mark Solution
Help us Help You!
Please don't delete messages or posts because it makes it impossible to understand what happened. If you don't want your messages to be seen then don't post here.
Please provide us with the version number of your client.
You can find it in the HA device info page after 'Firmware'.Make sure to provide detailed reports of bugs.
Please include error log uploads and info about the bug.
@Amadeo
This just happened, just came back from the store
It's c# too so it's not a memory leak
this is the last thing in the logs, before that it's normal activity e.g
2024-03-23 20:19:49.844 +02:00 [INF] [MEDIA] New state: Paused
2024-03-23 20:19:55.880 +02:00 [INF] [MEDIA] New state: Playing
2024-03-23 20:20:14.419 +02:00 [INF] [MEDIA] New state: Paused
So weird
i have 2x screens, they turn off at different times, there's screenshot sensors for them
I think it's related
What the actuall
The screenshot sensor resets to 0 for both of the screens when my screens go off or go into low power state(which basically "unplugs" theem)
What is the update time for them?
Has this happened before?
found more errors in the log
the RAM stuff first time, the screenshot sensor going to id 0 for both happens every time my monitors go off
How many GBs do you have? Is it using all of your ram? Seems extremely weird
I don't even have 20 to give it š
64, it was only using 20, firefox was using the rest
i have them set to 10 seconds at the moment, should I slow it down?
The rest! Nvm besides the point š
I have a similar setup in terms of monitors so I'll try turning them off with the sensors you mentioned enabled
this is how I have both configured, just that the other I set to id 1 every time
Na, even at 1s there should be no memory leak
again not sure if this is the cause, but my monitors were off when I came back, and it wasn't happening before I left
I just try to find the place where it may leak š
Can you post/send in pm all config for sensors/commands?
I'll run it in debugger tomorrow to see if I can spot anything
You can just send the config file which is in appdata Hass.agent
A lot easier than listing all of them
:Pah was just about to ask how to export them
can't believe i have to use codeblocks š
"sensors.json" and "config.json" in the config folder
ā¤ļø
Sanity check, if I ran a powershell script that was the issue powershell itself would be the process consuming all that RAM right?
I have a sneaky suspicion this is the screenshot one, will try to confirm tommorow and update
I have a bunch of powershell sensors and was wondering if they were causing it
Hard question, the process is spawned by hass.agent so it might ce counted as whole rather than separately
couldBut thats an educated guess
Would it show up as like a child of hass.agent maybe?š¤
I'd expect that (in task manager after "expanding" the details of the app)
But it would have to be a powershell sesnor that causes the ps to run constantly
So edge case
off topic: there's a setting to prevent discord from converting emotes
wait what?!
:P
oh yeah
okay sry about the thread but how did i not know this was a thing š¤£
Where's the setting?
ā¤ļø test
aw
Settings > Chat > Emoji > Second toggle
hm
running inf loop with screenshot sensors "insides" causes +-200 mb of ram usagage and garbage collector having not time to breathe
adding proper disposals (which should be done and I'll add that as a bugfix) makes it stay at 67 mb
but no apparent "mem leak"
I'll run mine via debuuger for some time and then configure the same set of commands/sensor and then repeat it
although without the custom ps script sensors ofc
yeah ill have to monitor it too, not sure what couldve caused it