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

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

----- Native stack trace -----

1: 0xab084b node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]

2: 0xe37f90 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, v8::OOMDetails const&) [node]

3: 0xe38364 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, v8::OOMDetails const&) [node]

4: 0x1057267 [node]

5: 0x106f2e9 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]

6: 0x1048ff7 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]

7: 0x1049c34 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]

8: 0x1029e2e v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]

9: 0x1478cac v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long, v8::internal::Isolate) [node]

10: 0x18a4ef6 [node]

Aborted

error building image: error building stage: failed to execute command: waiting for process to exit: exit status 134

exit status 134

View Deploy details

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

Solved

5 Replies

itsrems
EMPLOYEE

a year ago

Heya, could you share more information (project link, framework, etc) on this crash ?

At a first glance this might be some nodejs engine limitations, but it's hard to tell without more context.

Best,

Nico


Status changed to Awaiting User Response Railway 12 months ago


itsrems

Heya, could you share more information (project link, framework, etc) on this crash ?At a first glance this might be some nodejs engine limitations, but it's hard to tell without more context.Best,Nico

Basic Nuxt 3: e551ac48-0120-45fe-afcb-e2b9464115bc


Status changed to Awaiting Railway Response Railway 12 months ago


itsrems
EMPLOYEE

a year ago

Unfortunately this build error does not consist in a platform issue for Railway.

Please consider reverting to a stable commit and looking for issues with your recent changes.

Best,
Nico


Status changed to Awaiting User Response Railway 12 months ago


itsrems

Unfortunately this build error does not consist in a platform issue for Railway.Please consider reverting to a stable commit and looking for issues with your recent changes.Best,Nico

This is very strange, as the error only occurs with Railway. Neither locally, nor on another node ENV.


Status changed to Awaiting Railway Response Railway 12 months ago


itsrems
EMPLOYEE

a year ago

Are you able to monitor memory usage during build in another env ?


Status changed to Awaiting User Response Railway 12 months ago


Railway
BOT

6 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 6 months ago


Loading...