[BUG] oom crash

Resolved 💬 2 comments Opened Jun 3, 2025 by tassa-yoniso-manasi-karoto Closed Jun 4, 2025

Environment

  • Platform (select one):
  • [x ] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.9
  • Operating System: linux
  • Terminal: gnome

Bug Description

crash

Steps to Reproduce

  1. <!-- First step -->
  2. <!-- Second step -->
  3. <!-- And so on... -->

Expected Behavior

no crash duh

Actual Behavior

crash

Additional Context

only 8 words / 37 char in input field

! tree ./build
  ⎿  ./build
     ├── bin
     │   ├── langkit-0128
     │   ├── langkit-0202
     … +32 lines (ctrl+r to expand)

╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ > actually may be it has the same struc                                                                                                                                  │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
                                                                                                                                     ✓ Update installed · Restart to apply



<--- Last few GCs --->

[15418:0x23efb000] 77209148 ms: Mark-Compact (reduce) 2005.2 (2046.1) -> 2005.2 (2015.6) MB, pooled: 0 MB, 47.96 / 0.00 ms  (+ 0.6 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 649 ms) (average mu = 0.999, curr[15418:0x23efb000] 77211436 ms: Mark-Compact 2166.7 (2176.9) -> 2166.7 (2179.7) MB, pooled: 0 MB, 131.89 / 0.00 ms  (average mu = 0.995, current mu = 0.942) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

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

 1: 0xe1eff7 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0x121a420 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0x121a6f7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x144a235  [node]
 5: 0x1463aa9 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 6: 0x1438178 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 7: 0x14390a5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0x141140e v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
 9: 0x1400524 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Tagged<v8::internal::Map>, v8::internal::AllocationAlignment) [node]
10: 0x140242f v8::internal::FactoryBase<v8::internal::Factory>::NewRawTwoByteString(int, v8::internal::AllocationType) [node]
11: 0x141ce1a v8::internal::Factory::NewStringFromUtf8(v8::base::Vector<char const>, v8::internal::AllocationType) [node]
12: 0x12369ad v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [node]
13: 0xf8b6c3  [node]
14: 0x7f5957e0f845 
Aborted

claude code is the most buggy piece of software I have ever interacted with I think, please tell your management to hire more or sth. Last bug report from me o7.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗