I’ve been having this issue for the last several weeks where the amount of RAM Signal RGB takes continues to increase until it either crashes or I restart the application. It hasn’t happened too many times, but more than a coincidence at this point. Today it happened twice, first time it crashed before I was able to see how much RAM it was consuming, second time it took about 2.5 GB before I restarted it and now it’s back down to a few hundred MBs. The picture below is the time where it was the worst that I was able to catch…
@ArmenianBot - You’re not alone. If I leave it for a day, I get an error from Windows stating that I am out of memory. It caches over 40GB of memory and will not let go.
It kept happening and finally got so bad, I had to put a governor on it limiting it’s resources. It’s not perfect, and the occasional restart is kind of annoying, but it works. The sneaky thing is, it looks like it’s barely using anything, but it just keeps filling up the cache. No idea why.
Having the same issue here… after a few days, windows becomes borderline unresponsive and pops up a 0xc000012d error. After a minute or so, I can manage to get into task manager and see SignalRGB using over 15GB of ram. After ending the task, I can reopen it and everything goes back to normal. Been noticing this behavior for about a month now, fairly new.
@tk_mostly Thank you bro for the method, I finally found out this jerk vaporizing me 149G virtual mem.
@thekrynn - I just shared a grab of the solution I use - it’s been a huge improvement. Basically, as soon as the app reaches 1.5GB of virtual memory for more than 30 seconds, it automatically restarts the app. It happens so fast, the lights don’t even flicker on restart, and it doesn’t lose the network connection to some Govee lights I have.
This is fantastic… I literally set up an Asana task to ping me every 48 hrs to manually kill and restart the process, so this will work wonders. Setting it up tonight, much appreciated!
If you guys think it would help, I can show you all the settings I use in process lasso which keeps keeps the ram around 105-150 MB most of the time. Let me know!
Once I found the app to download (was a new one for me), the really only thing I had to figure out was right clicking on SignalRGB.exe and going to more > Set Watchdog Advanced Rules. From there, just copied your screenshot and took me a few seconds. Was very straightforward 
Totally! Obviously optional, but the other things I do are similar and keep it from ramping constantly and having the watchdog restart it. Thankfully, I have had zero issues since setting resource governing rules.
Caution though, I tried playing with CPU priority and throttling (in the More option) and… things got weird, so I leave those alone.
Govern memory priority
Enforce efficiency mode
Boost always off the same way.
I just wanted to throw out that my memory leak seemed to be related to the visualization I was using on my PC. I would creep up to 4GB over a couple of days, at which point I started having all kinds of other issues (32GB installed). After swapping to another effect, I have stayed solid at 350MB for almost a week.
Kinda crazy, even over a year later, it’s still trying to top my end-game SF server for RAM usage… I’m only using it to turn off all RGB rn too. Happens every 24H.
Just to be transparent, we haven’t received similar reports of excessive RAM usage recently, so this may be specific to your setup rather than a widespread issue.
What’s worth trying is switching the renderer from D3D12 to D3D11 in Settings, which can help with memory accumulation on some systems, and updating to the latest beta 2.5.64 is worth a shot.
I have the same problem. Just applied thread advice by setting boost, efficiency and priority. Will see how that goes. So far it’s keeping it at 845mb - 847mb. Before this it went up to 8Gb+.
Also keep in mind not everyone is tech savvy when it comes to RAM usage so reports will be low.
Your software isn’t exactly 100% user friendly yet either having to use custom setting to get my rig to work with Signal.
That’s fair feedback. We’ve been doing our best to make things as user friendly as possible with our tiny team of developers. Glad to hear you were able to adjust settings to get the RAM usage into expected levels.
If you have any bugs, reporting them in the app (upper-right corner) or through this link so that the support team can follow up goes a long way. It let’s us get #s and data so we can better understand the issue and finsd fixes.