# Memory leak in 2.5.72 — committed Private Bytes grows ~130 MB/hr (13 GB in 3.5 days), restart reclaims it **URL:** \ **Category:** Support\ **Created:** [July 23, 2026, 12:43pm UTC](https://forum.signalrgb.com/t/memory-leak-in-2-5-72-committed-private-bytes-grows-130-mb-hr-13-gb-in-3-5-days-restart-reclaims-it/9937 "2026-07-23T12:43:18Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![JimMcBubbles](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@JimMcBubbles](https://forum.signalrgb.com/u/JimMcBubbles)\ **Post date:** [July 23, 2026, 12:43pm UTC](https://forum.signalrgb.com/t/memory-leak-in-2-5-72-committed-private-bytes-grows-130-mb-hr-13-gb-in-3-5-days-restart-reclaims-it/9937/1 "2026-07-23T12:43:19Z")
SignalRGB 2.5.72, Win10, 32 GB RAM. SignalRgb.exe leaks committed private memory ~130 MB/hr (~3 GB/day), linear — reached 13.3 GB Private Bytes after ~3.5 days uptime but only ~0.22 GB working set. It’s committed, not resident, so it eats the Windows commit limit, not RAM. A prior run hit ~48 GB and caused commit-limit exhaustion (Event 2004 + a dwm.exe STATUS\_COMMITMENT\_LIMIT crash). Effect: Ruby, screen capture off. Restart reclaims all of it. Can share Perfmon/VMMap logs. ---
**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:** [July 23, 2026, 5:53pm UTC](https://forum.signalrgb.com/t/memory-leak-in-2-5-72-committed-private-bytes-grows-130-mb-hr-13-gb-in-3-5-days-restart-reclaims-it/9937/2 "2026-07-23T17:53:55Z")
Few things to try: 1. Test on our latest beta (Settings \> Updates \> Enroll in Preview Updates), see if it still happens 2. Close all other apps/browsers and run SignalRGB alone, does the growth rate change? 3. Does this happen on effects other than Ruby too?