Possible bug

[iulio]

What happened?

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

bug-report-history-1785030680821.json

i can send the heap snapshot if you want too.

it was supposed to fix a functionality.

Client information

• CLI Version: 0.52.0
• Git Commit: d14583b
• Session ID: 50741086-1857-48e9-9ae0-1ab007ee52cd
• Operating System: win32 v24.11.1
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-2.5
• Auth Type: oauth-personal
• Memory Usage: 10.52 GB
• Terminal Name: Unknown
• Terminal Background: #0c0c0c
• Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

[gemini-cli]

Effort Analysis:
The user reported a 'Memory Usage' of 10.52 GB RSS, which is recorded and formatted in packages/cli/src/ui/commands/bugCommand.ts and tracked via the MemoryMonitor in packages/core/src/telemetry/memory-monitor.ts. This value vastly exceeds the default Node.js heap limits and the 2 GB auto-snapshot threshold (MEMORY_SNAPSHOT_AUTO_THRESHOLD_BYTES) defined in packages/cli/src/ui/utils/memorySnapshot.ts. A leak of this magnitude (exceeding 10 GB) typically involves either unbounded growth in external memory (e.g., ArrayBuffers used for screenshots or file contents in packages/core/src/agents/browser/browserManager.ts) or a failure to dispose of heavy resources like multiple isolated browser instances or MCP server connections. Diagnosing the root cause requires deep analysis of V8 heap snapshots (provided by packages/core/src/telemetry/heap-snapshot.ts) and potentially investigating the ChatCompressionService in packages/core/src/context/chatCompressionService.ts or the history management in LocalAgentExecutor (packages/core/src/agents/local-executor.ts). The architectural complexity of tracing memory across asynchronous agent loops and external process integrations maps directly to the 'effort/large' classification.