fix: CPU leak from Bottleneck limiter accumulation + per-request optimizations

[soyelmismo]

Problem

Under heavy load (~5 min of intensive API usage), CPU grows ~0.1%/min until it hits ~2% and the server collapses. Root cause: Bottleneck rate limiter instances accumulate without cleanup — each creates a 250ms heartbeat interval that never stops.

Fix — 2 commits

1. CPU leak fix (+100 lines)

File	Change
	Evict idle Bottleneck limiters in using (was defined but never used). Populate on every call. Clean all 3 Maps consistently.
	FIFO eviction on (500), (200), (200). Per-target → in combo loops.
	Fix double-serialization. Conditional . Conditional usage logging.
	Eviction guards on and (500).
	Eviction guards on and (200).

2. Per-request optimizations extracted from perf branch (+97/-451 lines)

File	Change
	— walks object tree without . Consolidate settings read to single early call.
8 registries	Proxy lazy-init → direct (audio, embedding, image, moderation, music, rerank, search, video).

Mechanism of collapse

Testing

omniroute@3.8.7 typecheck:core
tsc --pretty false -p tsconfig.typecheck-core.json — 0 errors

• No business logic changes
• All eviction guards use FIFO (oldest first)
• uses optional chaining — zero cost when disabled

[gemini-code-assist]

Code Review

This pull request simplifies provider registries by replacing dynamic proxies with static exported constants, optimizes performance in chatCore.ts by replacing JSON.stringify with a fast size estimator and direct object references, and introduces eviction limits across various in-memory caches to prevent unbounded memory growth. The review feedback highlights a critical correctness issue across multiple files where cache eviction logic triggers on map size alone, which will prematurely evict valid entries when updating existing keys. Additionally, the feedback identifies a potential TypeError in chatCore.ts if provider is null, and suggests a performance optimization to avoid array allocations in the hot path of the new size estimator.

[kilo-code-bot]

Code Review Summary

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	2
SUGGESTION	1

Issue Details (click to expand)

WARNING

File	Line	Issue
open-sse/handlers/chatCore.ts	281	Potential infinite loop with circular references
open-sse/handlers/chatCore.ts	1546	JSON.stringify could throw on non-serializable values

Other Observations (not in diff)

Files Reviewed (8 files)

• open-sse/handlers/chatCore.ts - 2 issues
• open-sse/services/apiKeyRotator.ts - 0 issues
• open-sse/services/codexQuotaFetcher.ts - 0 issues
• open-sse/services/combo.ts - 0 issues
• open-sse/services/rateLimitManager.ts - 0 issues
• open-sse/config/audioRegistry.ts - 0 issues
• open-sse/config/embeddingRegistry.ts - 0 issues
• open-sse/config/imageRegistry.ts - 0 issues

---

_{Reviewed by laguna-m.1-20260312:free · 2,454,040 tokens}

[diegosouzapw]

Thank you for your contribution! This PR has been reviewed and integrated into the upcoming v3.8.8 release. 🎉