Reached heap limit Allocation failed - JavaScript heap out of memory

vhonoratoHOBBY

a year ago

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

yarn run v1.22.22

$ nest start

<--- Last few GCs --->

[36:0x2ea08d0] 5854 ms: Mark-sweep 252.5 (258.7) -> 251.9 (258.7) MB, 289.4 / 0.0 ms (average mu = 0.222, current mu = 0.007) allocation failure; scavenge might not succeed

[36:0x2ea08d0] 6221 ms: Mark-sweep 252.9 (258.7) -> 252.4 (259.2) MB, 364.4 / 0.0 ms (average mu = 0.102, current mu = 0.007) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

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

1: 0xab4728 node::Abort() [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

2: 0x9a4839 [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

3: 0xcc23e0 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

4: 0xcc27ab v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

5: 0xea6cc5 [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

6: 0xebb109 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

7: 0xe9789a v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

8: 0xe98c44 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

9: 0xe7934d v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

10: 0x12616eb v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long, v8::internal::Isolate) [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

11: 0x16abdf9 [/nix/store/5l687mklyr9rhhbvvpvi93zv0zbbi4vg-nodejs-18.18.2/bin/node]

Aborted (core dumped)

error Command failed with exit code 134.

View Deploy details

> ⓘ Deployment information is only viewable by Project members and Railway admins.

1 Replies

a year ago

If you need a service with more memory you would need to upgrade to Pro.


Reached heap limit Allocation failed - JavaScript heap out of memory - Railway Help Station