claude-code - 💡(How to fix) Fix [Bug] Performance degradation: operations taking 10-20x longer than baseline [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/sanzharal/.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-11T01:17:56.842Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/sanzharal/Documents/Programs/arenagenerator.\n at call (/$bunfs/root/src/entrypoints/cli.js:4458:7632)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:29:50.186Z"},{"error":"MaxFileReadTokenExceededError: File content (18809 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at ZY7 (/$bunfs/root/src/entrypoints/cli.js:4449:12671)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:29:57.250Z"},{"error":"Error: Request was aborted.\n at pE_ (/$bunfs/root/src/entrypoints/cli.js:1268:12089)\n at next (native:1:11)\n at sm7 (/$bunfs/root/src/entrypoints/cli.js:7918:9109)\n at next (native:1:11)\n at Hp7 (/$bunfs/root/src/entrypoints/cli.js:7923:11439)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:37:36.634Z"},{"error":"Error: Request was aborted.\n at pE_ (/$bunfs/root/src/entrypoints/cli.js:1268:12089)\n at next (native:1:11)\n at sm7 (/$bunfs/root/src/entrypoints/cli.js:7918:9109)\n at next (native:1:11)\n at Hp7 (/$bunfs/root/src/entrypoints/cli.js:7923:11439)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:37:40.866Z"},{"error":"Error: Request was aborted.\n at pE_ (/$bunfs/root/src/entrypoints/cli.js:1268:12089)\n at next (native:1:11)\n at sm7 (/$bunfs/root/src/entrypoints/cli.js:7918:9109)\n at next (native:1:11)\n at Hp7 (/$bunfs/root/src/entrypoints/cli.js:7923:11439)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:37:46.883Z"},{"error":"Error: Request was aborted.\n at pE_ (/$bunfs/root/src/entrypoints/cli.js:1268:12089)\n at next (native:1:11)\n at sm7 (/$bunfs/root/src/entrypoints/cli.js:7918:9109)\n at next (native:1:11)\n at Hp7 (/$bunfs/root/src/entrypoints/cli.js:7923:11439)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:38:11.016Z"},{"error":"Error: Request was aborted.\n at pE_ (/$bunfs/root/src/entrypoints/cli.js:1268:12089)\n at next (native:1:11)\n at sm7 (/$bunfs/root/src/entrypoints/cli.js:7918:9109)\n at next (native:1:11)\n at Hp7 (/$bunfs/root/src/entrypoints/cli.js:7923:11439)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T01:39:52.460Z"}]

TL;DR

The issue can be mitigated by addressing the "MaxFileReadTokenExceededError" and optimizing file reading processes.

Guidance

• Investigate the file reading process that is causing the "MaxFileReadTokenExceededError" and consider using offset and limit parameters to read specific portions of the file.
• Review the current working directory and file paths to ensure they are correct and existent, as indicated by the "File does not exist" error.
• Analyze the "Request was aborted" errors to determine if they are related to the file reading process or a separate issue.
• Consider checking for any resource-intensive operations or bottlenecks in the code that could be causing the slowdown.

Example

No specific code example can be provided without more context, but optimizing file reading processes could involve using streaming or buffering techniques to reduce memory usage and improve performance.

Notes

The provided error messages suggest that there are multiple issues at play, including file reading errors and request aborts. Addressing these issues may require a combination of code changes and optimizations.

Recommendation

Apply workaround by optimizing file reading processes and addressing the "MaxFileReadTokenExceededError" to mitigate the slowdown. This approach is recommended because it directly addresses the errors and issues presented in the problem, and can help to improve performance and stability.