I've been troubleshooting a persistent and reproducible resource exhaustion issue in Home Assistant across multiple platforms.

Originally, I deployed HA on a Raspberry Pi 4, where it intermittently ran out of resources and rebooted. Assuming hardware limitations, I migrated to a Windows 11 PC running VMware Workstation with significantly better specs — yet the issue persisted but not as frequently.

This weekend, I transitioned again to VirtualBox in hopes of isolating the fault, but the problem remained unchanged.

The breakthrough came after another out-of-memory error was shown on HA. I checked system resource usage and discovered HA was consuming over 8 GB of the 10 GB available RAM, with CPU usage spiking to 100%. Upon stopping a specific add-on, memory usage immediately dropped to ~1.8 GB and CPU returned to a stable ~9%.

This directly links the add-on to severe resource leakage. The issue clearly stems from the add-on, and stopping it resolves the symptoms instantly.

Others have reported nearly identical problems, citing “high memory consumption,” “memory leaks,” and “maxed-out CPU usage.” This strongly suggests a systemic bug either in the add-on or in how HA handles it.

This is not a hardware issue — it's a critical software-level defect that requires investigation and I believe this issue has been present for over a year its just taken me a very long time to actually spot the misbehaviour of the add on.

Add-on: Studio Code Server
Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.

Add-on version: 5.19.3
You are running the latest version of this add-on.
System: Home Assistant OS 15.2 (amd64 / qemux86-64)
Home Assistant Core: 2025.6.3
Home Assistant Supervisor: 2025.06.2

Now I only use this to edit my configuration.yaml file so I've disabled it for now but given that many people are reporting similar issues I know its not my setup