Skip to content

[BUG] VSCode Extension Crashes in Restart Loop with Large Conversation History (500+ sessions, 488MB)Retry #12221

Closed as duplicate

Description

@goandon

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Bug Description

The Claude Code VSCode Extension becomes completely unresponsive and enters a crash-reboot loop when the conversation history in ~/.claude/projects/ becomes large (500+ sessions, ~488MB).

What Should Happen?

Symptoms

  1. Extension Non-Responsive: Extension UI becomes completely unresponsive after loading
  2. Abnormal Termination and Restart Loop: Extension repeatedly crashes and attempts to restart
  3. MCP Server Initialization Failure: Console shows MCP error -32601: Method not found for the internal claude-vscode MCP server
  4. VSCode Hangs: In severe cases, VSCode itself becomes sluggish or unresponsive

Error Messages/Logs

### Error Logs

[ERROR] MCP server "claude-vscode" Failed to fetch tools: MCP error -32601: Method not found

Steps to Reproduce

Steps to Reproduce

  1. Use Claude Code CLI extensively over time (create 500+ conversation sessions)
  2. Accumulate ~488MB of conversation history in ~/.claude/projects/
  3. Install and launch Claude Code VSCode Extension
  4. Extension fails to initialize properly and enters crash-reboot loop
  5. Extension becomes unresponsive, VSCode may hang

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

  • not working after long commination

Claude Code Version

latest

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Root Cause

The extension appears to attempt loading ALL conversation history on startup without:

  • Pagination
  • Lazy loading
  • Timeout handling
  • Size limits

With 500+ sessions (488MB), this causes the initialization process to fail, resulting in MCP server errors and extension crashes.

Workaround

Delete conversation history folders:

rm -rf ~/.claude/projects/
rm -rf ~/.claude/debug/
rm -rf ~/.claude/todos/
rm -rf ~/.claude/shell-snapshots/

This freed 488MB and immediately resolved all issues.

Expected Behavior

The extension should:

  1. Implement pagination/lazy loading for conversation history
  2. Add size/count limits for history loading
  3. Provide graceful degradation when history is large
  4. Show meaningful error messages (not misleading MCP errors)
  5. Offer built-in history cleanup/archival functionality

Additional Notes

This is an edge case that only affects power users who extensively use Claude Code CLI. Most users won't encounter this issue, which may be why it hasn't been caught in testing.

However,

Activity

  1. github-actions commented on Nov 23, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] VS Code extension crashes with OOM error: conversation history accumulates to 700MB+ causing infinite crash loop #8722
    2. [BUG] VSCode Extension: Responses Not Rendering Due to MCP Server Error -32601 #11959
    3. Critical Memory Leak: Claude Code Consumed 129GB RAM and Caused System Freeze #11315

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. github-actions commented on Nov 27, 2025

    @github-actions

    This issue has been automatically closed as a duplicate of #8722.

    If this is incorrect, please re-open this issue or create a new one.

    🤖 Generated with Claude Code

  3. github-actions commented on Dec 4, 2025

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions