claude-code - 💡(How to fix) Fix [Bug] Incorrect application name display in macOS Activity Monitor with Japanese locale [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/bob/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T12:47:52.430Z"},{"error":"RangeError: stdout maxBuffer length exceeded\n at unknown\n at onData (node:child_process:153:110)\n at emit (node:events:95:22)\n at addChunk (internal:streams/readable:264:47)\n at readableAddChunkPushByteMode (internal:streams/readable:242:18)\n at handleArrayBufferViewResult (internal:streams/native-readable:79:16)\n at <anonymous> (internal:streams/native-readable:43:68)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T12:47:54.488Z"}]

TL;DR

The issue with the desktop app's name appearing weird in the activity manager under Japanese macOS may be related to encoding or localization issues.

Guidance

• Verify that the app's name is correctly encoded in the app's configuration files, such as the Info.plist file.
• Check the app's localization settings to ensure that the Japanese translation is correctly implemented.
• Investigate the error messages provided, specifically the "Lock acquisition failed" and "stdout maxBuffer length exceeded" errors, to see if they are related to the issue.
• Review the app's code to ensure that it correctly handles non-ASCII characters in the app's name.

Example

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

Notes

The issue may be specific to the Japanese macOS environment, and further investigation is needed to determine the root cause. The error messages provided do not directly relate to the issue, but may be worth investigating to ensure they are not contributing to the problem.

Recommendation

Apply workaround: The issue may be resolved by adjusting the app's localization settings or encoding, but without further information, it is difficult to provide a specific solution.