Starting Container

yarn run v1.22.22

$ nest start

<--- Last few GCs --->

[25:0x337e6d0] 8050 ms: Mark-sweep (reduce) 252.6 (258.9) -> 252.3 (258.9) MB, 186.2 / 0.0 ms (average mu = 0.195, current mu = 0.005) allocation failure; GC in old space requested

[25:0x337e6d0] 8272 ms: Mark-sweep (reduce) 252.7 (258.9) -> 252.5 (258.9) MB, 193.8 / 0.0 ms (average mu = 0.166, current mu = 0.129) allocation failure; GC in old space requested

<--- JS stacktrace --->

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

1: 0xac22d8 node::Abort() [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

2: 0x9ad387 [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

3: 0xcccdd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

4: 0xccd1ab v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

5: 0xec4a45 [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

6: 0xec4b31 [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

7: 0xed9e62 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*, v8::GCCallbackFlags) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

8: 0xedaa2a v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

9: 0xeb4e35 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

10: 0xeb6204 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

11: 0xe9490b v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

12: 0xe8a65c v8::internal::FactoryBase::NewFixedArrayWithMap(v8::internal::Handle, int, v8::internal::AllocationType) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

13: 0x117458b v8::internal::MaybeHandle v8::internal::OrderedHashTable::Allocate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

14: 0x117463c v8::internal::MaybeHandle v8::internal::OrderedHashTable::Rehash(v8::internal::Isolate*, v8::internal::Handle, int) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

15: 0x1296a32 v8::internal::Runtime_SetGrow(int, unsigned long, v8::internal::Isolate) [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

16: 0x17087b9 [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

Aborted

error Command failed with exit code 134.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

container event container died

yarn run v1.22.22

$ nest start

<--- Last few GCs --->

[25:0x3e076d0] 7565 ms: Mark-sweep (reduce) 252.3 (258.9) -> 252.1 (258.9) MB, 227.8 / 0.0 ms (average mu = 0.305, current mu = 0.292) allocation failure; GC in old space requested

[25:0x3e076d0] 7840 ms: Mark-sweep (reduce) 252.3 (258.9) -> 252.2 (258.9) MB, 206.7 / 0.0 ms (average mu = 0.279, current mu = 0.249) allocation failure; GC in old space requested

<--- JS stacktrace --->

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

1: 0xac22d8 node::Abort() [/nix/store/kr6p8nmj3y4wmfm3q6f0j8yd2zb2lxaj-nodejs-18.20.2/bin/node]

Can you explain what it is possible to be from this error?

View Deploy details

> ⓘ Deployment information is only viewable by project members and Railway employees.