Skip to content
SignalRGB

Memory Usage Issues

SignalRGB’s memory usage should remain stable during normal operation. If you notice memory usage growing continuously over hours or days, or if the system becomes sluggish the longer SignalRGB runs, you may be experiencing a memory issue.

Symptoms

Section titled “Symptoms”
  • RAM usage for SignalRGB increases steadily over time without returning to baseline
  • System becomes slow or unresponsive after SignalRGB has been running for many hours
  • SignalRGB crashes after extended use
  • Other applications start showing “out of memory” errors while SignalRGB is running

What to Try First

Section titled “What to Try First”
  1. Minimize to the system tray — clicking the X in the top-right corner of the application window minimizes SignalRGB to the system tray and reduces memory usage.
  2. Update SignalRGB — memory issues in previous versions may already be fixed. Check Settings > Application > Updates and install any available update.
  3. Restart SignalRGB — restarting returns memory usage to baseline if a leak is present.
  4. Choose an effect without Screen Capture — Screen Capture effects process video frames continuously and can contribute to higher memory usage. Switching to a non-Screen Capture effect may reduce memory consumption.
  5. Reduce effects complexity — very large canvases with many devices and complex effects use more memory. Try simplifying the layout temporarily to see if usage stabilizes.

Checking Memory Usage

Section titled “Checking Memory Usage”
  1. Press CTRL + SHIFT + ESC to open Task Manager.
  2. Go to the Details tab.
  3. Find Signal.exe and SignalRgbLauncher.exe.
  4. Watch the Memory column over time. If the number grows continuously without dropping, that indicates a memory leak.

Reporting a Memory Leak

Section titled “Reporting a Memory Leak”

If memory usage grows consistently and restarting SignalRGB is the only resolution, report it to the team:

  1. Note the SignalRGB version (Settings > About).
  2. Note the effect(s) active when the leak occurs.
  3. Collect the log files from %localappdata%\VortxEngine\app-VERSION\Signal-x64\Logs\.
  4. Submit a bug report using the in-app bug report. This is the fastest way for the team to receive your logs and diagnose the issue. See Contact Customer Support for instructions on submitting a ticket.
Section titled “Related Articles”