FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

luke · July 11, 2019, 1:23am

@BrunoQuaresma and @szokrika, this could be the following issue:

Build fail with heap out of memory error in gatsby 2.11.6

opened 01:10PM - 30 Jun 19 UTC

closed 11:00AM - 10 Jul 19 UTC

## Description With Gatsby version 2.11.6 I can`t build a production version …of the app because it fails with out of memory exception while building (same on my machine and on Netlify). If I downgrade to version 2.10.5, build is working as expected. ### Steps to reproduce Run `rimraf .cache public && gatsby build` ### Expected result Build should succeed ### Actual result Build fails with out of memory error : ⠦ Building production JavaScript and CSS bundles <--- Last few GCs ---> [10733:0x10264e000] 241422 ms: Scavenge 1331.0 (1423.1) -> 1330.1 (1423.6) MB, 12.4 / 0.0 ms (average mu = 0.123, current mu = 0.086) allocation failure [10733:0x10264e000] 241437 ms: Scavenge 1331.1 (1423.6) -> 1330.2 (1424.1) MB, 12.0 / 0.0 ms (average mu = 0.123, current mu = 0.086) allocation failure [10733:0x10264e000] 241458 ms: Scavenge 1331.3 (1424.1) -> 1330.4 (1424.6) MB, 14.7 / 0.0 ms (average mu = 0.123, current mu = 0.086) allocation failure <--- JS stacktrace ---> ==== JS stack trace ========================================= 0: ExitFrame [pc: 0x2e6bd9b5be3d] Security context: 0x261c7219e6e9 <JSObject> 1: /* anonymous */(aka /* anonymous */) [0x261c46282299] [/Users/ssijak/work/hocudabudem.fit/node_modules/gatsby/node_modules/@babel/core/lib/transformation/file/merge-map.js:~155] [pc=0x2e6bdaf5a89b](this=0x261c319822b1 <null>,m=0x261c8d43ed71 <Object map = 0x261cf880a9c9>) 2: arguments adaptor frame: 3->1 3: forEach [0x261c72186df1](this=0x261c... FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 0x10003c597 node::Abort() [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 2: 0x10003c7a1 node::OnFatalError(char const*, char const*) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 3: 0x1001ad575 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 4: 0x100579242 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 5: 0x10057bd15 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 6: 0x100577bbf v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 7: 0x100575d94 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 8: 0x10058262c v8::internal::Heap::AllocateRawWithLigthRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 9: 0x1005826af v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 10: 0x100551ff4 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 11: 0x1007da044 v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/ssijak/.nvm/versions/node/v10.15.3/bin/node] 12: 0x2e6bd9b5be3d 13: 0x2e6bdaf5a89b /bin/sh: line 1: 10733 Abort trap: 6 gatsby build error Command failed with exit code 134. ### Environment System: OS: macOS 10.14.5 CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz Shell: 5.3 - /bin/zsh Binaries: Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node Yarn: 1.15.2 - ~/.nvm/versions/node/v10.15.3/bin/yarn npm: 6.4.1 - ~/.nvm/versions/node/v10.15.3/bin/npm Languages: Python: 2.7.10 - /usr/bin/python Browsers: Chrome: 75.0.3770.100 Safari: 12.1.1 npmPackages: gatsby: 2.10.5 => 2.10.5 gatsby-awesome-pagination: ^0.3.4 => 0.3.4 gatsby-background-image: ^0.7.4 => 0.7.4 gatsby-image: ^2.2.3 => 2.2.3 gatsby-plugin-favicon: ^3.1.6 => 3.1.6 gatsby-plugin-feed: ^2.3.1 => 2.3.1 gatsby-plugin-google-tagmanager: ^2.1.0 => 2.1.0 gatsby-plugin-lunr: ^1.5.1 => 1.5.1 gatsby-plugin-manifest: ^2.2.0 => 2.2.0 gatsby-plugin-netlify: ^2.1.0 => 2.1.0 gatsby-plugin-netlify-cms: ^4.1.0 => 4.1.0 gatsby-plugin-offline: ^2.2.0 => 2.2.0 gatsby-plugin-postcss: ^2.1.0 => 2.1.0 gatsby-plugin-prefetch-google-fonts: ^1.4.2 => 1.4.2 gatsby-plugin-purgecss: ^4.0.0 => 4.0.0 gatsby-plugin-react-helmet: ^3.1.0 => 3.1.0 gatsby-plugin-robots-txt: ^1.4.0 => 1.4.0 gatsby-plugin-sharp: ^2.2.1 => 2.2.1 gatsby-plugin-sitemap: ^2.2.1 => 2.2.1 gatsby-remark-copy-linked-files: ^2.1.0 => 2.1.0 gatsby-remark-embed-video: ^1.7.1 => 1.7.1 gatsby-remark-images: ^3.1.2 => 3.1.2 gatsby-remark-relative-images: ^0.2.2 => 0.2.2 gatsby-remark-responsive-image: ^1.0.0-alpha13-alpha.435e0178 => 1.0.0-alpha13-alpha.435e0178 gatsby-source-filesystem: ^2.1.1 => 2.1.1 gatsby-transformer-remark: ^2.5.0 => 2.5.0 gatsby-transformer-sharp: ^2.2.0 => 2.2.0 npmGlobalPackages: gatsby: 2.10.0

Topic		Replies	Views
[Support Guide] What can I do if my build fails for memory-overallocation-related errors? Support Guides building , support-guide	1	7752	December 1, 2025
Gatsby build error from Git Support building , gatsby	8	2271	June 28, 2022
Build command - JavaScript heap out of memory Support building , deployment	6	12414	August 27, 2023
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory Support building , deployment , netlify-newbie	9	6497	October 30, 2023
Gatsby v4 Builds suddenly killed, exit code 137 Support gatsby	33	4715	January 5, 2023

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Related topics