›_ Claude Code Issues
Claude Code Issues / #12670

[BUG] [P0 CRITICAL] Server-side corruption after MCP incident causing compression crashes

Resolved 💬 2 comments Opened Nov 29, 2025 by Adapa2025 Closed Dec 4, 2025

Preflight Checklist

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

What's Wrong?

Summary

Critical P0 bug affecting both Claude Desktop and claude.ai (web) - short conversations incorrectly flagged as "too long", triggering inappropriate compression followed by complete system crash ("black hole"). Claude Code (CLI) unaffected - confirming server-side issue.

Critical Context: Linked to Prior MCP Incident

Timeline:

  • Nov 28, 2025: MCP filesystem misconfiguration generated 37,338 files (482 MB) in APPDATA\Claude
  • Nov 29, 2025 (24h later): Compression crashes began on Desktop + Web

Hypothesis: User account server-side state corrupted/overloaded from MCP incident. Local cleanup performed but server-side state persists.

Reproduction Steps

  1. Open Claude Desktop OR claude.ai
  2. Start new conversation
  3. Exchange a few messages (short conversation)
  4. Observe: system judges conversation "too long"
  5. Observe: compression triggered
  6. Result: Complete crash/black hole on ALL platforms (Desktop + Web)

Test Results

  • ❌ Claude Desktop: CRASHES
  • ❌ Claude.ai (Web): CRASHES IDENTICALLY
  • ✅ Claude Code (CLI): Works normally

Conclusion: Server-side backend issue (compression, contextual memory) affecting Desktop/Web but not CLI.

Impact

  • ⛔ Total loss of Desktop + Web functionality
  • ⛔ Professional project blocked (ADAPA - 260 PDFs, 2027 deadline)
  • ⛔ User forced to CLI-only workflow

Additional Symptoms (Desktop)

  • Missing Claude Code icon in interface
  • 10 zombie Claude processes consuming massive CPU (PID 7076: 1346 CPU!)
  • Files regenerating after cleanup (23,315 files → 273 files even after uninstall)

Detailed Documentation

I've created comprehensive reports available on GitHub:

Repository: https://github.com/Adapa2025/Anunnaki-Les-origines-/tree/claude/fix-conversation-compression-01GsnG7J4Wt1smm6BGwRRsQ2

Key documents:

  1. BUG_REPORT_CLAUDE_DESKTOP.md - Complete bug report
  2. CORRELATION_INCIDENTS_MCP_COMPRESSION.md - Detailed MCP correlation analysis
  3. COMMENT_SIGNALER_BUG.md - Submission guide

Immediate Actions Requested

  1. 🚨 Investigate user account server-side state (account: Adapa2025)
  2. 🚨 Reset/clean user profile server-side if corrupted
  3. 🚨 Review server CPU/memory metrics for Nov 29, 2025 morning
  4. 🚨 Investigate MCP ↔ compression interaction handling
  5. 🚨 Add circuit breaker to compression process

Environment

  • User: Marc (Adapa2025)
  • OS: Windows
  • Date: November 29, 2025
  • Affected: Desktop + Web
  • Working: CLI only
  • Prior incidents: User reports recurring CPU issues pattern

Priority Justification

  • P0: Complete Desktop/Web loss
  • Multi-platform: Affects all non-CLI interfaces
  • User account corruption: Likely affects server-side state
  • Professional impact: Blocking critical project work

---

Note: User mentions "De nouveau un problème de CPU?" ("Again a CPU problem?") - suggesting recurring pattern of similar incidents.
Demander: Reset profil utilisateur serveur

What Should Happen?

Summary

Critical P0 bug affecting both Claude Desktop and claude.ai (web) - short conversations incorrectly flagged as "too long", triggering inappropriate compression followed by complete system crash ("black hole"). Claude Code (CLI) unaffected - confirming server-side issue.

Critical Context: Linked to Prior MCP Incident

Timeline:

  • Nov 28, 2025: MCP filesystem misconfiguration generated 37,338 files (482 MB) in APPDATA\Claude
  • Nov 29, 2025 (24h later): Compression crashes began on Desktop + Web

Hypothesis: User account server-side state corrupted/overloaded from MCP incident. Local cleanup performed but server-side state persists.

Reproduction Steps

  1. Open Claude Desktop OR claude.ai
  2. Start new conversation
  3. Exchange a few messages (short conversation)
  4. Observe: system judges conversation "too long"
  5. Observe: compression triggered
  6. Result: Complete crash/black hole on ALL platforms (Desktop + Web)

Test Results

  • ❌ Claude Desktop: CRASHES
  • ❌ Claude.ai (Web): CRASHES IDENTICALLY
  • ✅ Claude Code (CLI): Works normally

Conclusion: Server-side backend issue (compression, contextual memory) affecting Desktop/Web but not CLI.

Impact

  • ⛔ Total loss of Desktop + Web functionality
  • ⛔ Professional project blocked (ADAPA - 260 PDFs, 2027 deadline)
  • ⛔ User forced to CLI-only workflow

Additional Symptoms (Desktop)

  • Missing Claude Code icon in interface
  • 10 zombie Claude processes consuming massive CPU (PID 7076: 1346 CPU!)
  • Files regenerating after cleanup (23,315 files → 273 files even after uninstall)

Detailed Documentation

I've created comprehensive reports available on GitHub:

Repository: https://github.com/Adapa2025/Anunnaki-Les-origines-/tree/claude/fix-conversation-compression-01GsnG7J4Wt1smm6BGwRRsQ2

Key documents:

  1. BUG_REPORT_CLAUDE_DESKTOP.md - Complete bug report
  2. CORRELATION_INCIDENTS_MCP_COMPRESSION.md - Detailed MCP correlation analysis
  3. COMMENT_SIGNALER_BUG.md - Submission guide

Immediate Actions Requested

  1. 🚨 Investigate user account server-side state (account: Adapa2025)
  2. 🚨 Reset/clean user profile server-side if corrupted
  3. 🚨 Review server CPU/memory metrics for Nov 29, 2025 morning
  4. 🚨 Investigate MCP ↔ compression interaction handling
  5. 🚨 Add circuit breaker to compression process

Environment

  • User: Marc (Adapa2025)
  • OS: Windows
  • Date: November 29, 2025
  • Affected: Desktop + Web
  • Working: CLI only
  • Prior incidents: User reports recurring CPU issues pattern

Priority Justification

  • P0: Complete Desktop/Web loss
  • Multi-platform: Affects all non-CLI interfaces
  • User account corruption: Likely affects server-side state
  • Professional impact: Blocking critical project work

---

Note: User mentions "De nouveau un problème de CPU?" ("Again a CPU problem?") - suggesting recurring pattern of similar incidents.

Error Messages/Logs

## Summary

Critical P0 bug affecting **both Claude Desktop and claude.ai (web)** - short conversations incorrectly flagged as "too long", triggering inappropriate compression followed by complete system crash ("black hole"). **Claude Code (CLI) unaffected** - confirming server-side issue.

## Critical Context: Linked to Prior MCP Incident

**Timeline:**
- **Nov 28, 2025**: MCP filesystem misconfiguration generated **37,338 files (482 MB)** in APPDATA\Claude
- **Nov 29, 2025** (24h later): Compression crashes began on Desktop + Web

**Hypothesis**: User account server-side state corrupted/overloaded from MCP incident. Local cleanup performed but server-side state persists.

## Reproduction Steps

1. Open Claude Desktop OR claude.ai
2. Start new conversation
3. Exchange a few messages (short conversation)
4. Observe: system judges conversation "too long"
5. Observe: compression triggered
6. **Result**: Complete crash/black hole on ALL platforms (Desktop + Web)

## Test Results

- ❌ **Claude Desktop**: CRASHES
- ❌ **Claude.ai (Web)**: CRASHES IDENTICALLY  
- ✅ **Claude Code (CLI)**: Works normally

**Conclusion**: Server-side backend issue (compression, contextual memory) affecting Desktop/Web but not CLI.

## Impact

- ⛔ **Total loss of Desktop + Web functionality**
- ⛔ Professional project blocked (ADAPA - 260 PDFs, 2027 deadline)
- ⛔ User forced to CLI-only workflow

## Additional Symptoms (Desktop)

- Missing Claude Code icon in interface
- 10 zombie Claude processes consuming massive CPU (PID 7076: 1346 CPU!)
- Files regenerating after cleanup (23,315 files → 273 files even after uninstall)

## Detailed Documentation

I've created comprehensive reports available on GitHub:

**Repository**: https://github.com/Adapa2025/Anunnaki-Les-origines-/tree/claude/fix-conversation-compression-01GsnG7J4Wt1smm6BGwRRsQ2

**Key documents:**
1. `BUG_REPORT_CLAUDE_DESKTOP.md` - Complete bug report
2. `CORRELATION_INCIDENTS_MCP_COMPRESSION.md` - Detailed MCP correlation analysis
3. `COMMENT_SIGNALER_BUG.md` - Submission guide

## Immediate Actions Requested

1. 🚨 **Investigate user account server-side state** (account: Adapa2025)
2. 🚨 **Reset/clean user profile server-side** if corrupted
3. 🚨 **Review server CPU/memory metrics** for Nov 29, 2025 morning
4. 🚨 **Investigate MCP ↔ compression interaction** handling
5. 🚨 **Add circuit breaker** to compression process

## Environment

- **User**: Marc (Adapa2025)
- **OS**: Windows
- **Date**: November 29, 2025
- **Affected**: Desktop + Web
- **Working**: CLI only
- **Prior incidents**: User reports recurring CPU issues pattern

## Priority Justification

- **P0**: Complete Desktop/Web loss
- **Multi-platform**: Affects all non-CLI interfaces
- **User account corruption**: Likely affects server-side state
- **Professional impact**: Blocking critical project work

---

**Note**: User mentions *"De nouveau un problème de CPU?"* ("Again a CPU problem?") - suggesting **recurring pattern** of similar incidents.

Steps to Reproduce

Summary

Critical P0 bug affecting both Claude Desktop and claude.ai (web) - short conversations incorrectly flagged as "too long", triggering inappropriate compression followed by complete system crash ("black hole"). Claude Code (CLI) unaffected - confirming server-side issue.

Critical Context: Linked to Prior MCP Incident

Timeline:

  • Nov 28, 2025: MCP filesystem misconfiguration generated 37,338 files (482 MB) in APPDATA\Claude
  • Nov 29, 2025 (24h later): Compression crashes began on Desktop + Web

Hypothesis: User account server-side state corrupted/overloaded from MCP incident. Local cleanup performed but server-side state persists.

Reproduction Steps

  1. Open Claude Desktop OR claude.ai
  2. Start new conversation
  3. Exchange a few messages (short conversation)
  4. Observe: system judges conversation "too long"
  5. Observe: compression triggered
  6. Result: Complete crash/black hole on ALL platforms (Desktop + Web)

Test Results

  • ❌ Claude Desktop: CRASHES
  • ❌ Claude.ai (Web): CRASHES IDENTICALLY
  • ✅ Claude Code (CLI): Works normally

Conclusion: Server-side backend issue (compression, contextual memory) affecting Desktop/Web but not CLI.

Impact

  • ⛔ Total loss of Desktop + Web functionality
  • ⛔ Professional project blocked (ADAPA - 260 PDFs, 2027 deadline)
  • ⛔ User forced to CLI-only workflow

Additional Symptoms (Desktop)

  • Missing Claude Code icon in interface
  • 10 zombie Claude processes consuming massive CPU (PID 7076: 1346 CPU!)
  • Files regenerating after cleanup (23,315 files → 273 files even after uninstall)

Detailed Documentation

I've created comprehensive reports available on GitHub:

Repository: https://github.com/Adapa2025/Anunnaki-Les-origines-/tree/claude/fix-conversation-compression-01GsnG7J4Wt1smm6BGwRRsQ2

Key documents:

  1. BUG_REPORT_CLAUDE_DESKTOP.md - Complete bug report
  2. CORRELATION_INCIDENTS_MCP_COMPRESSION.md - Detailed MCP correlation analysis
  3. COMMENT_SIGNALER_BUG.md - Submission guide

Immediate Actions Requested

  1. 🚨 Investigate user account server-side state (account: Adapa2025)
  2. 🚨 Reset/clean user profile server-side if corrupted
  3. 🚨 Review server CPU/memory metrics for Nov 29, 2025 morning
  4. 🚨 Investigate MCP ↔ compression interaction handling
  5. 🚨 Add circuit breaker to compression process

Environment

  • User: Marc (Adapa2025)
  • OS: Windows
  • Date: November 29, 2025
  • Affected: Desktop + Web
  • Working: CLI only
  • Prior incidents: User reports recurring CPU issues pattern

Priority Justification

  • P0: Complete Desktop/Web loss
  • Multi-platform: Affects all non-CLI interfaces
  • User account corruption: Likely affects server-side state
  • Professional impact: Blocking critical project work

---

Note: User mentions "De nouveau un problème de CPU?" ("Again a CPU problem?") - suggesting recurring pattern of similar incidents.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.0.1307.0

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗