arktype icon indicating copy to clipboard operation
arktype copied to clipboard

Starting with version [email protected] svelte-check fails with memory related error

Open RonenEizen opened this issue 3 months ago • 1 comments

Report a bug

After updating arktype to version 2.1.21 my svelte-check fails with the error below. Version 2.1.20 works just fine.

🔎 Search Terms

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

🧩 Context

  • ArkType version: 2.1.21
  • TypeScript version (5.1+): 5.9.2
  • Other context you think may be relevant (JS flavor, OS, etc.): svelte-kit

Error message:

Getting Svelte diagnostics...


<--- Last few GCs --->

[49589:0x130008000]   197766 ms: Mark-Compact 4041.0 (4130.0) -> 4025.0 (4130.8) MB, pooled: 1 MB, 2142.62 / 0.0
0 ms  (average mu = 0.065, current mu = 0.029) allocation failure; scavenge might not succeed
[49589:0x130008000]   200071 ms: Mark-Compact 4041.5 (4130.8) -> 4025.4 (4131.0) MB, pooled: 1 MB, 2252.46 / 0.0
0 ms  (average mu = 0.045, current mu = 0.023) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x100bd3484 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/opt/homebrew/Cellar/nvm/0.40.3/versi
ons/node/v22.15.0/bin/node]
 2: 0x100d99a48 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails co
nst&) [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node]
 3: 0x100fa79a0 v8::internal::Heap::stack() [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node]
 4: 0x100fbde18 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectio
nReason, v8::GCCallbackFlags)::$_1::operator()() const [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/b
in/node]
 5: 0x100fbd6ac void heap::base::Stack::SetMarkerAndCallbackImpl<v8::internal::Heap::CollectGarbage(v8::internal
::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags)::$_1>(heap::base::Stack*, void*, 
void const*) [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node]
 6: 0x101777420 PushAllRegistersAndIterateStack [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node
]
 7: 0x100fa5b60 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectio
nReason, v8::GCCallbackFlags) [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node]
 8: 0x100f9a328 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType
, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/opt/homebrew/Cellar/nvm/0.40.3/versions/n
ode/v22.15.0/bin/node]
 9: 0x100f9ab60 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationTyp
e, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/opt/homebrew/Cellar/nvm/0.40.3/versions/
node/v22.15.0/bin/node]
10: 0x100f7de80 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::All
ocationType, v8::internal::AllocationOrigin) [/opt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node]
11: 0x10139955c v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/o
pt/homebrew/Cellar/nvm/0.40.3/versions/node/v22.15.0/bin/node]
12: 0x101859af4 Builtins_CEntry_Return1_ArgvOnStack_NoBuiltinExit [/opt/homebrew/Cellar/nvm/0.40.3/versions/node
/v22.15.0/bin/node]
13: 0x10832ad58 
14: 0x108408e20 
15: 0x10828a7c4 
16: 0x1081cfbd0 
17: 0x108408590
...

RonenEizen avatar Sep 23 '25 21:09 RonenEizen

2.1.21 only adds a few line of code for StandardJSONSchema support, so it seems extremely unlikely it would be the version itself that is causing the problem.

My best guess is possibly you ended up with multiple installations somehow if 2.1.20 is still specified or allowed elsewhere, and some comparison between Types across versions is causing the problem.

ssalbdivad avatar Sep 24 '25 16:09 ssalbdivad

I have the same issue.

joleeee avatar Nov 28 '25 00:11 joleeee