Skip to main content

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

Our team has a CRA application and we are using the following script to build locally and in bitbucket pipelines

node --max-old-space-size=8192 scripts/build.js

We are all getting this error now with our source code

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x111336665 node::Abort() (.cold.1) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 2: 0x11002f1c9 node::Abort() [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 3: 0x11002f3ae node::OOMErrorHandler(char const*, bool) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 4: 0x1101a41d0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 5: 0x1101a4193 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 6: 0x1103458e5 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 7: 0x11034992d v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 8: 0x11034620d v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
 9: 0x11034372d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
10: 0x110350b10 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
11: 0x110350b91 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
12: 0x11031dc27 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
13: 0x1106d574e v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
14: 0x110a7e499 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]
15: 0x110aad486 Builtins_FastNewFunctionContextFunction [/Users/apple/.nvm/versions/node/v16.20.0/bin/node]

We disabled source maps in the webpack config and its still failing. We tried setting the following to false in the webpack.config.js file

// Source maps are resource heavy and can cause out of memory issue for large source files.
const shouldUseSourceMap = false

Using higher than 8GB is not doable with our current infrastructure building using node on bitbucket pipelines which is capped at 8GB of memory.

On a tight deadline with this blocker. Any ideas? Thanks!

Via Active questions tagged javascript - Stack Overflow https://ift.tt/6avZLAM
Labels:

Comments

Post a Comment

Popular posts from this blog

Prop `className` did not match in next js app

I have written a sample code ( Github Link here ). this is a simple next js app, but giving me error when I refresh the page. This seems to be the common problem and I tried the fix provided in the internet but does not seem to fix my issue. The error is Warning: Prop className did not match. Server: "MuiBox-root MuiBox-root-1" Client: "MuiBox-root MuiBox-root-2". Did changes for _document.js, modified _app.js as mentioned in official website and solutions in stackoverflow. but nothing seems to work. Could someone take a look and help me whats wrong with the code? Via Active questions tagged javascript - Stack Overflow https://ift.tt/2FdjaAW
Post a Comment
Read more

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype
Post a Comment
Read more

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console
Post a Comment
Read more