Memory leak in 2.5.72 — committed Private Bytes grows ~130 MB/hr (13 GB in 3.5 days), restart reclaims it

Support
1

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.

2

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?