# Memory leak (bad auto conflicting process closing?) **URL:** \ **Category:** Support\ **Tags:** issues\ **Created:** [July 22, 2024, 10:28pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637 "2024-07-22T22:28:26Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![redguy27](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@redguy27](https://forum.signalrgb.com/u/redguy27)\ **Post date:** [July 22, 2024, 10:28pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/1 "2024-07-22T22:28:26Z")
Preface: I did not take screenshots, but I’m more than happy to add some if it helps. I think this is the root cause of [this issue](https://forum.signalrgb.com/t/memory-leak-in-signalrgb-on-windows-11/1052). I built a new rig, installed SignalRGB for the first time on any rig, and for some reason after ~24 hours of uptime task manager would say that my entire 48GB of ram was in use, even though there were no running processes. Sparing the countless pointless rabbit holes, eventually I checked RAMMap and noticed that page tables were consuming an _insane_ amount of RAM, so checking the process list in that I noticed **thousands** of `cmd.exe` and `tasklist.exe` processes that were open (each holding a 32kB page table). Given that I don’t have a whole lot of things installed, I figured given `tasklist` was present it was probably the auto conflicting process killer in SignalRGB that was leaving these processes open. I turned the auto killer off, and now my memory issues are solved. Maybe some force killing of the spawned processes is necessary here. ---
**Author:** ![HarDBR](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/hardbr/32/282_2.png) [@HarDBR](https://forum.signalrgb.com/u/HarDBR)\ **Post date:** [July 24, 2024, 5:36pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/2 "2024-07-24T17:36:09Z")
Hi, @redguy27 It’s been a long time ago that we replace our process conflict routine, which version are you on? Is L-Connect running in background? We have identified a similar issue on LConnect. ---
**Author:** ![Matt](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/matt/32/13_2.png) [@Matt](https://forum.signalrgb.com/u/Matt)\ **Post date:** [July 24, 2024, 5:49pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/3 "2024-07-24T17:49:03Z")
I’ve recently seen this in windows 11 with L-Connect3. Tasklist and cmd run once per second and leak 32kb pagefiles. Not sure if it’s an L-Connect bug, or a windows bug, but something is definitely wrong there. If you watch rammap you can see the launched shell processes, but you have to hunt. ---
**Author:** ![danmus](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@danmus](https://forum.signalrgb.com/u/danmus)\ **Post date:** [October 30, 2024, 3:15pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/4 "2024-10-30T15:15:37Z")
![image_2024-10-30_201125449](https://us1.discourse-cdn.com/flex015/uploads/signalrgb/original/2X/e/e5884f81e74430cec4c40d87bbb10b0c308438cc.png) SignalRGB - version 2.4.22 L-connect 3 - version 2.0.16 Windows 11 I have a leek too ---
**Author:** ![joseashb](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@joseashb](https://forum.signalrgb.com/u/joseashb)\ **Post date:** [November 25, 2024, 10:59pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/5 "2024-11-25T22:59:26Z")
SignalRGB - version 2.4.35 Windows 10 22H2 Huge memory leak as seen in screenshot ![SignalRGB](https://us1.discourse-cdn.com/flex015/uploads/signalrgb/original/2X/2/25bab7757af6f0b20692d997eb713cdc8dd6b4a0.png) ---
**Author:** ![joseashb](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@joseashb](https://forum.signalrgb.com/u/joseashb)\ **Post date:** [June 25, 2026, 2:02pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/6 "2026-06-25T14:02:05Z")
Issue is linked to the effects being used. Certain effects doesn’t produce same behavior. ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [June 25, 2026, 5:24pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/7 "2026-06-25T17:24:32Z")
Just wanted to check, is this still happening for you, or did you manage to get it sorted? Happy to dig into it further if it still persists. ---
**Author:** ![joseashb](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@joseashb](https://forum.signalrgb.com/u/joseashb)\ **Post date:** [June 26, 2026, 7:55pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/8 "2026-06-26T19:55:48Z")
I found out, that the memory leak issue all depends on the effects being used, while others don’t cause the specified issue. So far none of the base provided effects causes memory leak. But many from the shop (free ones tested) have memory leaks over time (about 6hr+). I’ll try to test it out and get logs, but currently facing another issue where once I signin the app, the app crash and goes into startup loop ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [June 27, 2026, 5:35pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/9 "2026-06-27T17:35:37Z")
What app version are you on right now? Please try these: 1. Download and install Microsoft Visual C++ Redistributable x64 from **[Microsoft’s website](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-supported-redistributable-version)**. 2. Complete a **[full power cycle](https://docs.signalrgb.com/troubleshooting/hardware-drivers/full-power-cycle/#_top)**. ---
**Author:** ![joseashb](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@joseashb](https://forum.signalrgb.com/u/joseashb)\ **Post date:** [June 27, 2026, 8:37pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/10 "2026-06-27T20:37:08Z")
Power cycle or restarting eliminates the memory leak early, does not mean its not present. I did all the testing and debugging I could on my end to pinpoint that the issue is related to The effects downloaded from shop (free ones). ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [June 28, 2026, 4:48pm UTC](https://forum.signalrgb.com/t/memory-leak-bad-auto-conflicting-process-closing/2637/11 "2026-06-28T16:48:42Z")
Is it just specific effects, or all the free ones listed? I’d suggest sending this as a bug report through the bug icon found on the upper right corner of the app so we can look into it further with logs.