# H Company — VRAM Ghost Busting: Who You Gonna close() ?

- Company: H Company (hcompany.ai)
- Announced: 2026-06-25
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://hcompany.ai/newsroom/vram-ghost-busting-who-you-gonna-close
- Record: https://forck.live/items/23616-vram-ghost-busting-who-you-gonna-close
- Subject: Holo

H Company engineers diagnosed recurring phantom GPU memory usage on SkyPilot-managed Kubernetes nodes. On freshly booked nodes, nvidia-smi showed tens of gigabytes of allocated VRAM with no owning process. The root cause was zombie training containers whose threads were stuck in an uninterruptible D-state waiting for a FUSE filesystem reply; the kubelet could not reap those containers, and the underlying GPU memory allocation remained pinned.

## Evidence

Verbatim from https://hcompany.ai/newsroom/vram-ghost-busting-who-you-gonna-close:

> Every single D-state thread was sleeping inside the same kernel function: request_wait_answer . That symbol is defined in `fs/fuse/dev.c` , i.e. the FUSE device driver. It is the function that parks a thread until the userspace FUSE daemon answers a request (more details about FUSE below).

---

Record: https://forck.live/items/23616-vram-ghost-busting-who-you-gonna-close
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md