claude-code - 💡(How to fix) Fix [Bug] Severe latency in Claude Code with long-context sessions (20min+ turn times) [2 comments, 1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/thedemings/.local/share/claude/versions/2.1.105 (expected in multi-process scenarios)\n at bd_ (/$bunfs/root/src/entrypoints/cli.js:2334:2153)\n at nt6 (/$bunfs/root/src/entrypoints/cli.js:2334:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-14T03:09:25.240Z"},{"error":"Error: 1P event logging: 14 events failed to export (code=ECONNABORTED, timeout of 10000ms exceeded)\n at queueFailedEvents (/$bunfs/root/src/entrypoints/cli.js:422:2574)\n at async doExport (/$bunfs/root/src/entrypoints/cli.js:422:1516)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-14T03:44:44.693Z"},{"error":"Error: 1P event logging: 15 events failed to export (code=ECONNABORTED, timeout of 10000ms exceeded)\n at queueFailedEvents (/$bunfs/root/src/entrypoints/cli.js:422:2574)\n at async doExport (/$bunfs/root/src/entrypoints/cli.js:422:1516)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-14T03:45:04.709Z"}]

TL;DR

The severe latency in Claude Code sessions may be mitigated by investigating and addressing potential causes such as API/inference latency spikes, prompt cache misses, or Opus 4.6 throughput under heavy load.

Guidance

• Investigate the Error: NON-FATAL: Lock acquisition failed message to determine if it's related to the latency issue, potentially indicating a multi-process scenario conflict.
• Examine the 1P event logging errors with code=ECONNABORTED to see if event export timeouts are contributing to the delay, possibly due to network or server response issues.
• Consider sharing the session ID or /status output to help identify the root cause of the latency.
• Review the conversation context and subagent calls to determine if the complexity of the session is contributing to the latency.

Example

No code snippet is provided as the issue does not explicitly mention a specific code-related problem.

Notes

The provided errors and environment information suggest a complex issue with multiple potential causes. Further investigation is needed to determine the root cause of the latency.

Recommendation

Apply workaround: Investigate and address potential causes such as API/inference latency spikes, prompt cache misses, or Opus 4.6 throughput under heavy load, as the issue seems to be related to the specific session and environment rather than a straightforward version upgrade.