Harshal Patel 7f9455628a internal/oom: Fix memory leak by removing watcher from map on Stop ...

The oomWatchers.Stop method stopped the watcher but never removed
it from the watchers map. Because Add is the only writer and nothing
ever deletes from the map, *watcher entries accumulated for the lifetime
of the shim process. This resulted in an unbounded memory leak.
Furthermore, this prevented the same container ID from ever being watched
again if it was re-created, silently dropping OOM monitoring.

This commit modifies Stop to delete(ows.watchers, cid), ensuring the
watcher is released and the container ID is freed.

Signed-off-by: Harshal Patel <106813066+HarshalPatel1972@users.noreply.github.com>

2026-07-28 04:46:48 +05:30

..

oom.go

*: move new oom package into internal

2026-01-06 20:44:04 -05:00

utils.go

*: move new oom package into internal

2026-01-06 20:44:04 -05:00

watcher_test.go

internal/oom: Fix memory leak by removing watcher from map on Stop

2026-07-28 04:46:48 +05:30

watcher.go

internal/oom: Fix memory leak by removing watcher from map on Stop

2026-07-28 04:46:48 +05:30