[Connector] Network monitoring process leak & throttle instance accumulation

[Flegma]

Summary

Background processes and throttle instances accumulate without cleanup.

Findings

• network.service.ts — each NIC spawns 2 bash processes running indefinitely. Only killed on SIGTERM. Reinitializations orphan previous processes.
• throttle.ts — global throttlers Map accumulates instances with setInterval forever. Never cleaned up.

Impact

Zombie bash processes accumulate. Memory/CPU consumed by stale throttle intervals.

Suggested Fix

Store process references and kill before creating new. Use Node.js fs.read instead of bash. Add LRU/TTL for throttler cleanup.

---

Related Issues (Memory Leak Pattern)

• [API] Missing NestJS lifecycle cleanup — intervals, recursive timeouts, stale WS refs #375 — [API] Missing NestJS lifecycle cleanup
• [Web] GraphQL subscription leaks — NotificationStore, ApplicationSettings, Matchmaking, MatchLobby #385 — [Web] GraphQL subscription leaks
• [Web] Socket listeners & component event handlers never cleaned up #386 — [Web] Socket listeners never cleaned up
• [Game Server] Resource disposal — HttpClient, WebSocket, Timer, pending messages accumulation #398 — [Game Server] Resource disposal issues
• [Connector] Network monitoring process leak & throttle instance accumulation #407 — [Connector] Network process leak & throttle accumulation