Renderer process memory leak — 2.5 GB RAM + 70% CPU within 4 minutes on fresh session (Windows 11) #28680

Activity

1. github-actions

   assigned

   Hona

   on May 21, 2026
2. github-actions commented on May 21, 2026

   

   github-actionsBot

   on May 21, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Memory Megathread #20695: Memory Megathread — the maintainers have created a central tracking issue for memory-related problems. They are actively collecting heap snapshots there to diagnose runaway memory growth. Please follow the instructions in that issue to provide a heap snapshot, which will greatly help track down the root cause.
   • v1.4.3: runaway memory growth followed by recursive Zig panic and deliberate ud2 trap in renderer/title path #22084: Similar runaway memory growth leading to OOM/crash in renderer path (different OS, but related symptoms)

   If your issue is specifically about the renderer process consuming excessive RAM/CPU, the Memory Megathread (#20695) is the best place to contribute — it includes instructions for capturing heap snapshots that the team needs to diagnose these issues.
3. github-actions commented on Jul 21, 2026

   

   github-actionsBot

   on Jul 21, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
4. github-actions

   closed this as not plannedon Jul 21, 2026