CommandCodeAI / CommandCodeAI/command-code

macOS client crashes

未關閉
#650 3 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

Summary

Command Code "cmd" binary crashes after ~10s.

Unfortunately I got excited and instantly bought the "GOAT" plan to test this new tool out but I couldn't launch the application.

I installed it using "npm i -g command-code", then ran "cmd login" to login. I entered a directory and ran "cmd" to start the application and left it untouched, after 10s the app crashed with a big output message.

Expected Behavior

Command Code launches and I can enjoy my subscription.

Actual Behavior

<--- Last few GCs --->

[24453:0x7a6c80c000] 10674 ms: Mark-Compact 4056.4 (4185.9) -> 4056.3 (4185.9) MB, pooled: 8.2 MB, 9.10 / 0.00 ms (average mu = 0.939, current mu = 0.880) allocation failure; scavenge might not succeed
[24453:0x7a6c80c000] 10696 ms: Mark-Compact 4093.8 (4224.0) -> 4093.8 (4224.0) MB, pooled: 8.2 MB, 7.96 / 0.00 ms (average mu = 0.909, current mu = 0.644) allocation failure; scavenge might not succeed

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x100ac8590 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
2: 0x100d2b000 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
3: 0x100f77d40 v8::internal::Heap::stack() [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
4: 0x100f75cc4 v8::internal::Heap::CheckMemoryPressure() [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
5: 0x100f6ac0c std::__1::invoke_result<v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment, v8::internal::AllocationHint)::$_0&>::type v8::internal::HeapAllocator::CollectGarbageAndRetryAllocation<v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment, v8::internal::AllocationHint)::$_0&>(v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment, v8::internal::AllocationHint)::$_0&, v8::internal::AllocationType) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
6: 0x100f68af8 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment, v8::internal::AllocationHint) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
7: 0x100f36034 v8::internal::FactoryBasev8::internal::Factory::NewRawOneByteString(unsigned int, v8::internal::AllocationType, v8::internal::AllocationHint) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
8: 0x100f4b160 v8::internal::Factory::NewStringFromUtf8(v8::base::Vector, unibrow::Utf8Variant, v8::internal::AllocationType) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
9: 0x100d42964 v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
10: 0x100bfd5b8 node::(anonymous namespace)::MakeString(v8::Isolate*, char const*, unsigned long, node::encoding) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
11: 0x100bfd524 node::StringDecoder::DecodeData(v8::Isolate*, char const*, unsigned long*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
12: 0x100bfd9e4 node::(anonymous namespace)::DecodeData(v8::FunctionCallbackInfov8::Value const&) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
13: 0x10192b3cc Builtins_CallApiCallbackOptimizedNoProfiling [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
14: 0x1254e0bf8
15: 0x12546ddbc
16: 0x1019674c4 Builtins_AsyncFunctionAwaitResolveClosure [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
17: 0x101a3e058 Builtins_PromiseFulfillReactionJob [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
18: 0x101956920 Builtins_RunMicrotasks [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
19: 0x101926850 Builtins_JSRunMicrotasksEntry [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
20: 0x100ea7944 v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
21: 0x100ea81e0 v8::internal::(anonymous namespace)::InvokeWithTryCatch(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
22: 0x100ea8304 v8::internal::Execution::TryRunMicrotasks(v8::internal::Isolate*, v8::internal::MicrotaskQueue*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
23: 0x102be7250 v8::internal::MicrotaskQueue::RunMicrotasks(v8::internal::Isolate*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
24: 0x102be7598 v8::internal::MicrotaskQueue::PerformCheckpoint(v8::Isolate*) (.cold.1) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
25: 0x100ed6e84 v8::internal::MicrotaskQueue::PerformCheckpoint(v8::Isolate*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
26: 0x1009d600c node::InternalCallbackScope::Close() [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
27: 0x1009d5988 node::InternalCallbackScope::~InternalCallbackScope() [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
28: 0x102b115e8 node::fs::FSReqPromise<node::AliasedBufferBase<double, v8::Float64Array>>::Resolve(v8::Localv8::Value) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
29: 0x100acfb9c node::fs::AfterInteger(uv_fs_s*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
30: 0x100abe468 node::MakeLibuvRequestCallback<uv_fs_s, void ()(uv_fs_s)>::Wrapper(uv_fs_s*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
31: 0x101900740 uv__work_done [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
32: 0x1019043cc uv__async_io [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
33: 0x10191853c uv__io_poll [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
34: 0x101904950 uv_run [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
35: 0x1009d75b0 node::SpinEventLoopInternal(node::Environment*) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
36: 0x102b357ac node::NodeMainInstance::Run() (.cold.1) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
37: 0x100b0b0c8 node::NodeMainInstance::Run() [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
38: 0x100a8758c node::Start(int, char**) [/Users/alkhatib/.nvm/versions/node/v25.4.0/bin/node]
39: 0x1807f3bec start [/usr/lib/dyld]
zsh: abort cmd

Steps to reproduce the issue
  1. Install the app using "npm i -g command-code@latest"
  2. Login using "cmd login"
  3. Change the cwd to your project directory
  4. Run "cmd" to start the app
  5. Wait ~10s
  6. Watch it crash...
Command Code Version

1.14.1

Operating System

macOS

Terminal/IDE

iterm2

Shell

zsh

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

I'm running "macOS 27 Golden Gate", though this issue occurred to other users too.

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

在 macOS 上使用 zsh 透過 command-code@latest 1.14.1 重現:執行 cmd login,進入專案目錄,啟動 cmd,然後等待約 10 秒。從 cmd CLI 進入點和回報的 Node.js heap-out-of-memory trace 開始。完成標準是,在回報的設定下用戶端持續執行,而不是因 out-of-memory 錯誤中止。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
javascript, node.js
領域
cli
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
42/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。