claude-code - 💡(How to fix) Fix [Bug] Memory leak on macOS and Linux [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/orianasfeir/.local/share/claude/versions/2.1.116 (expected in multi-process scenarios)\n at jl_ (/$bunfs/root/src/entrypoints/cli.js:2752:2177)\n at B88 (/$bunfs/root/src/entrypoints/cli.js:2752:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T06:36:53.147Z"},{"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-22T06:49:28.244Z"}]

TL;DR

The memory leak issue on mac and linux may be related to the lock acquisition failure, and a potential workaround could be to investigate and resolve the locking mechanism.

Guidance

• Investigate the locking mechanism in the cli.js file, specifically around line 2752, to understand why the lock acquisition is failing.
• Check the file system permissions and access rights for the /Users/orianasfeir/.local/share/claude/versions/2.1.116 directory to ensure that the process has the necessary permissions to acquire the lock.
• Review the error logs to see if there are any patterns or correlations between the lock acquisition failures and the memory leak.
• Consider implementing a retry mechanism or a fallback strategy to handle cases where the lock acquisition fails.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The provided information is limited, and the root cause of the memory leak is not explicitly stated. The suggested guidance is based on the error messages and may not directly address the memory leak issue.

Recommendation

Apply workaround: The lock acquisition failure error suggests that there may be an issue with the locking mechanism, and resolving this issue may help mitigate the memory leak. However, without further information, it is difficult to provide a definitive solution.