[BUG] memory leak issue

Start by reproducing the growth with the supplied Docker Compose configuration and monitor it with docker stats. Compare the 2026.3-or-newer image with the reported Python 3.14.6 workaround, then read the referenced Home Assistant issue for the suspected regression. Done should identify whether the container image is responsible and document or validate the resulting fix.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Since 2026.3 there is a memory leak, a workarround seams to be python 3.14.6 version.
Reference: https://github.com/home-assistant/core/issues/165953

Expected Behavior

No response

Steps To Reproduce

1. on the environment
2. run the container with version 2026.3 or greater
3. wait 1 minute and the container will grow to multiple Gb of ram.

Environment

- OS: Ubuntu server 24.04
- How docker service was installed: distro's packagemanager

CPU architecture

x86-64

Docker creation

using docker-compose:
service:
  homeassistant:
    image: lscr.io/linuxserver/homeassistant:latest
    container_name: homeassistant
    mem_limit: 1g
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TZ
    cap_add:
      - NET_ADMIN
      - NET_RAW
    volumes:
      - ./config/:/config
      - /etc/localtime:/etc/localtime:ro
      - /var/run/udev:/run/udev
      - /run/dbus:/run/dbus:ro
      - /run/audio:/run/audio:ro
      - /etc/machine-id:/etc/machine-id:ro
    ports:
      - 8123:8123 #optional
    privileged: true

Container logs

docker stats | grep home
homeassistant             4.66%     1.283GiB / 6GiB  21.39%