claude-code - 💡(How to fix) Fix [Bug] Prompt caching not properly persisting across sessions with large contexts [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/zsoltjanos/.local/share/claude/versions/2.1.124 (expected in multi-process scenarios)\n at n68 (/$bunfs/root/src/entrypoints/cli.js:2770:2177)\n at aM6 (/$bunfs/root/src/entrypoints/cli.js:2770:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T06:30:15.253Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T08:11:11.834Z"}]

TL;DR

The issue may be related to caching and lock acquisition failures, and a potential workaround could be to clear the cache or check for lock file issues.

Guidance

• Investigate the lock acquisition failure error and check if there are any lock files present in the /home/zsoltjanos/.local/share/claude/versions/2.1.124 directory that may be causing the issue.
• Verify if the caching mechanism is properly configured and if the cache is being cleared or updated correctly after a certain period of inactivity.
• Check the cli.js file at lines 2770:2177 and 50:3448 to understand the lock acquisition and request abortion logic.
• Consider clearing the cache or restarting the application to see if it resolves the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to a specific version (2.1.124) and platform (linux), so the solution may not be applicable to other versions or platforms. Additionally, the error messages suggest a multi-process scenario, which may require special handling.

Recommendation

Apply workaround: Clear the cache or check for lock file issues, as it is a safer approach given the limited information available.