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”- Update SignalRGB — memory issues in previous versions may already be fixed. Check Settings > Application > Updates and install any available update.
- Restart SignalRGB — restarting returns memory usage to baseline if a leak is present.
- Disable Screen Capture — screen capture effects that process video frames continuously can contribute to higher memory usage. Try switching to a non-screen-capture effect and monitor memory usage.
- 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”- Press
CTRL + SHIFT + ESCto open Task Manager. - Go to the Details tab.
- Find
Signal.exeandSignalRgbLauncher.exe. - 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:
- Note the SignalRGB version (Settings > About).
- Note the effect(s) active when the leak occurs.
- Collect the log files from
%localappdata%\VortxEngine\app-VERSION\Signal-x64\Logs\. - Submit a bug report via the in-app bug icon or the community forum.