claude-code - 💡(How to fix) Fix [Bug] Ultrareview crashes during deduplication phase and returns zero findings on large codebases [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/arno/.local/share/claude/versions/2.1.123 (expected in multi-process scenarios)\n at x86 (/$bunfs/root/src/entrypoints/cli.js:2769:2177)\n at Jw8 (/$bunfs/root/src/entrypoints/cli.js:2769:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T09:11:01.723Z"},{"error":"Error: 1: Command failed with ERR_STREAM_PREMATURE_CLOSE: code --force --install-extension anthropic.claude-code\nPremature close \n at _Q1 (/$bunfs/root/src/entrypoints/cli.js:1717:4046)\n at async ec1 (/$bunfs/root/src/entrypoints/cli.js:1717:1435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T09:11:03.094Z"}]

TL;DR

Investigate lock acquisition failures and premature close errors to resolve the Ultrareview crashes and inconsistent findings.

Guidance

• Review the error logs to understand the sequence of events leading to the crashes, focusing on the "Lock acquisition failed" and "ERR_STREAM_PREMATURE_CLOSE" errors.
• Verify that the /Users/arno/.local/share/claude/versions/2.1.123 directory is accessible and not locked by another process, which might be causing the "Lock acquisition failed" error.
• Check the system resources and terminal configuration to ensure they are not contributing to the premature close errors.
• Consider re-running the Ultrareview sessions with increased logging or debugging enabled to gather more detailed information about the crashes.

Example

No specific code snippet is provided as the issue seems to be related to the Ultrareview tool's internal functionality and system interactions.

Notes

The provided error messages suggest issues with lock acquisition and premature closes, which might be related to the tool's multi-process handling or system resource limitations. However, without more detailed information about the Ultrareview tool and its configuration, it's challenging to provide a definitive solution.

Recommendation

Apply workaround: Re-run the failed sessions with increased logging and debugging to gather more information, and consider reaching out to the Ultrareview support team for further assistance, as the issue might be specific to the tool or its interaction with the system environment.