A device with its memory taken and nothing computing is usually a process that has allocated and then gone to sleep, or one that died without releasing.
1. Confirm both numbersOverview: memory near total, utilization near zero. If utilization is N/A rather than zero, the vendor is reporting nothing and that is a different problem.
2. Find the allocationOpen the device. The process table shows the memory each process holds; the inline trend beside it says whether that has been flat or growing.
3. Check for an owner that has goneA pod that no longer exists with memory still held is a driver or runtime leak. The Kubernetes tab says whether the pod is still there.
4. Look for the moment it filledHistory on memory: a step is an allocation, a ramp is a leak, and a flat line since boot is something that started with the machine.
5. Take it furtherNothing in siltide will free it. What it gives you is the pid, the pod, and the minute it happened.