claude-code - 💡(How to fix) Fix [Bug] Claude 3.5 Sonnet performance degradation compared to previous behavior [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/bytedance/.local/share/claude/versions/2.1.101 (expected in multi-process scenarios)\n at Oc_ (/$bunfs/root/src/entrypoints/cli.js:2836:2153)\n at Ve6 (/$bunfs/root/src/entrypoints/cli.js:2836:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T02:56:32.724Z"},{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:528:2814)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T03:06:22.412Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at T (/$bunfs/root/src/entrypoints/cli.js:531:242)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:531:456)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:528:2885)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-12T03:06:22.413Z"}]

TL;DR

The issue may be resolved by adjusting the search path or pattern to prevent ripgrep timeouts.

Guidance

• The errors suggest that ripgrep is timing out after 20 seconds, which may be due to a broad search path or pattern.
• Try searching a more specific path or pattern to reduce the load on ripgrep.
• The "Lock acquisition failed" error may be related to multi-process scenarios, but it's unclear if this is the primary cause of the issue.
• Verify that the search is working correctly by testing with a simpler query.

Example

No code snippet is provided as the issue does not clearly imply a specific code change.

Notes

The issue may be related to the version or configuration of ripgrep, but this is not explicitly stated. Further investigation into the search parameters and environment may be necessary to fully resolve the issue.

Recommendation

Apply workaround: Adjust the search path or pattern to prevent ripgrep timeouts, as this is the most direct and likely solution based on the provided errors.