The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process

Support
,
1

Site Name:- https://frosty-borg-2ff62d.netlify.app

We’ve had a build timeout issue before and had gotten our build time limit increased. This seems like a different issue though because increasing the build time last time fixed the problem.

Now the logs state the build fails in about 3-4 minutes with the error mentioned in the title. After this error is shown, the build log seems to run for another 40-45 minutes and then finally dies.

Not sure what the problem here is. Does the time need to be increased again?

Any assistance is appreciated.

10:47:11 AM: Build ready to start
10:47:20 AM: build-image version: 1ac2360cf8aee6cb2695dd2682b312fefc908a7f (xenial)
10:47:20 AM: build-image tag: v3.15.0
10:47:20 AM: buildbot version: fe6512288e75c8fa5aadaebb51ed1f96e9314fd4
10:47:20 AM: Building without cache
10:47:20 AM: Starting to prepare the repo for build
10:47:20 AM: No cached dependencies found. Cloning fresh repo
10:47:20 AM: git clone https://github.com/sapienlife2021/sapien.systems
10:47:21 AM: Preparing Git Reference refs/heads/master
10:47:21 AM: Parsing package.json dependencies
10:47:22 AM: Starting build script
10:47:22 AM: Installing dependencies
10:47:22 AM: Python version set to 2.7
10:47:23 AM: Downloading and installing node v16.14.2...
10:47:23 AM: Downloading https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.xz...
10:47:23 AM: Computing checksum with sha256sum
10:47:23 AM: Checksums matched!
10:47:25 AM: Now using node v16.14.2 (npm v8.5.0)
10:47:26 AM: Started restoring cached build plugins
10:47:26 AM: Finished restoring cached build plugins
10:47:26 AM: Attempting ruby version 2.7.2, read from environment
10:47:26 AM: Using ruby version 2.7.2
10:47:26 AM: Using PHP version 5.6
10:47:27 AM: No npm workspaces detected
10:47:27 AM: Started restoring cached node modules
10:47:27 AM: Finished restoring cached node modules
10:47:27 AM: Installing NPM modules using NPM version 8.5.0
10:47:28 AM: npm WARN old lockfile
10:47:28 AM: npm WARN old lockfile The package-lock.json file was created with an old version of npm,
10:47:28 AM: npm WARN old lockfile so supplemental metadata must be fetched from the registry.
10:47:28 AM: npm WARN old lockfile
10:47:28 AM: npm WARN old lockfile This is a one-time fix-up, please be patient...
10:47:28 AM: npm WARN old lockfile
10:47:36 AM: npm WARN EBADENGINE Unsupported engine {
10:47:36 AM: npm WARN EBADENGINE   package: 'strapi-plugin-wysiwsg-react-md-editor@1.0.3',
10:47:36 AM: npm WARN EBADENGINE   required: { node: '>=10.16.0 <=14.x.x', npm: '>=6.0.0' },
10:47:36 AM: npm WARN EBADENGINE   current: { node: 'v16.14.2', npm: '8.5.0' }
10:47:36 AM: npm WARN EBADENGINE }
10:47:43 AM: npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
10:47:44 AM: npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
10:47:44 AM: npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
10:47:44 AM: npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
10:47:45 AM: npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
10:47:45 AM: npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
10:47:46 AM: npm WARN deprecated rollup-plugin-babel@4.4.0: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
10:47:46 AM: npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
10:47:47 AM: npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
10:47:49 AM: npm WARN deprecated strapi-plugin-wysiwsg-react-md-editor@1.0.3: The package is renamed to https://www.npmjs.com/package/strapi-plugin-wysiwyg-react-md-editor
10:47:49 AM: npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
10:47:51 AM: npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
10:47:52 AM: npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained
10:47:52 AM: npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained
10:47:52 AM: npm WARN deprecated @hapi/address@2.1.4: Moved to 'npm install @sideway/address'
10:47:53 AM: npm WARN deprecated @npmcli/fs@1.1.0: this version had an improper engines field added, update to 1.1.1
10:47:53 AM: npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
10:47:54 AM: npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
10:47:54 AM: npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
10:47:55 AM: npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
10:47:55 AM: npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
10:47:55 AM: npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
10:47:56 AM: npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
10:47:56 AM: npm WARN deprecated @hapi/joi@15.1.1: Switch to 'npm install joi'
10:47:58 AM: npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
10:48:05 AM: npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
10:48:06 AM: npm WARN deprecated core-js-pure@3.21.0: core-js-pure@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js-pure.
10:48:06 AM: npm WARN deprecated core-js@3.21.0: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
10:48:08 AM: added 2125 packages, and audited 2126 packages in 41s
10:48:08 AM: 207 packages are looking for funding
10:48:08 AM:   run `npm fund` for details
10:48:08 AM: 43 vulnerabilities (1 low, 4 moderate, 27 high, 11 critical)
10:48:08 AM: To address issues that do not require attention, run:
10:48:08 AM:   npm audit fix
10:48:08 AM: To address all issues possible (including breaking changes), run:
10:48:08 AM:   npm audit fix --force
10:48:08 AM: Some issues need review, and may require choosing
10:48:08 AM: a different dependency.
10:48:08 AM: Run `npm audit` for details.
10:48:08 AM: NPM modules installed
10:48:08 AM: Started restoring cached go cache
10:48:08 AM: Finished restoring cached go cache
10:48:08 AM: go version go1.14.4 linux/amd64
10:48:08 AM: go version go1.14.4 linux/amd64
10:48:08 AM: Installing missing commands
10:48:08 AM: Verify run directory
10:48:09 AM: ​
10:48:09 AM: ────────────────────────────────────────────────────────────────
10:48:09 AM:   Netlify Build                                                 
10:48:09 AM: ────────────────────────────────────────────────────────────────
10:48:09 AM: ​
10:48:09 AM: ❯ Version
10:48:09 AM:   @netlify/build 27.9.1
10:48:09 AM: ​
10:48:09 AM: ❯ Flags
10:48:09 AM:   baseRelDir: true
10:48:09 AM:   buildId: 62edf9578fac9d0573d76dca
10:48:09 AM:   deployId: 62edf9578fac9d0573d76dcc
10:48:09 AM:   systemLogFile: 3
10:48:09 AM: ​
10:48:09 AM: ❯ Current directory
10:48:09 AM:   /opt/build/repo
10:48:09 AM: ​
10:48:09 AM: ❯ Config file
10:48:09 AM:   No config file was defined: using default values.
10:48:09 AM: ​
10:48:09 AM: ❯ Context
10:48:09 AM:   production
10:48:09 AM: ​
10:48:09 AM: ────────────────────────────────────────────────────────────────
10:48:09 AM:   1. Build command from Netlify app                             
10:48:09 AM: ────────────────────────────────────────────────────────────────
10:48:09 AM: ​
10:48:09 AM: $ npm run build
10:48:09 AM: > sapienpartner@0.1.0 build
10:48:09 AM: > react-scripts build
10:48:11 AM: Creating an optimized production build...
10:48:11 AM: Browserslist: caniuse-lite is outdated. Please run:
10:48:11 AM:   npx browserslist@latest --update-db
10:48:11 AM:   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
10:51:30 AM: The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
10:51:30 AM: ​
10:51:30 AM: ────────────────────────────────────────────────────────────────
10:51:30 AM:   "build.command" failed                                        
10:51:30 AM: ────────────────────────────────────────────────────────────────
10:51:30 AM: ​
10:51:30 AM:   Error message
10:51:30 AM:   Command failed with exit code 1: npm run build (https://ntl.fyi/exit-code-1)
10:51:30 AM: ​
10:51:30 AM:   Error location
10:51:30 AM:   In Build command from Netlify app:
10:51:30 AM:   npm run build
10:51:30 AM: ​
10:51:30 AM:   Resolved config
10:51:30 AM:   build:
10:51:30 AM:     command: npm run build
10:51:30 AM:     commandOrigin: ui
10:51:30 AM:     environment:
10:51:30 AM:       - NODE_VERSION
10:51:30 AM:       - REACT_APP_CLOUDFLARE_URL
10:51:30 AM:       - REACT_APP_S3_ACCESS_KEY
10:51:30 AM:       - REACT_APP_S3_BUCKET_NAME
10:51:30 AM:       - REACT_APP_S3_BUCKET_REGION
10:51:30 AM:       - REACT_APP_S3_PREFIX_NAME
10:51:30 AM:       - REACT_APP_S3_SECRET_KEY
10:51:30 AM:       - REACT_APP_URL
10:51:30 AM:     publish: /opt/build/repo/build
10:51:30 AM:     publishOrigin: ui
10:51:31 AM: Caching artifacts
10:51:31 AM: Started saving node modules
10:51:31 AM: Finished saving node modules
10:51:31 AM: Started saving build plugins
10:51:31 AM: Finished saving build plugins
10:51:31 AM: Started saving pip cache
10:51:31 AM: Finished saving pip cache
10:51:31 AM: Started saving emacs cask dependencies
10:51:31 AM: Finished saving emacs cask dependencies
10:51:31 AM: Started saving maven dependencies
10:51:31 AM: Finished saving maven dependencies
10:51:31 AM: Started saving boot dependencies
10:51:31 AM: Finished saving boot dependencies
10:51:31 AM: Started saving rust rustup cache
10:51:31 AM: Finished saving rust rustup cache
10:51:31 AM: Started saving go dependencies
10:51:31 AM: Finished saving go dependencies
11:35:12 AM: Build exceeded maximum allowed runtime
2

Hiya @TK1,

Hard to tell exactly what is happening, without a specific deploy to look at. Mind sharing a recent deploy ID that failed (last part of the URL in our UI’s deploy logs URL for that deploy), so we can check memory usage in our monitors to confirm? In the future, if you’ll link to your deploy logs instead of (or in addition to) copy-pasting them, that will help us help you more quickly.

But that message about running out of memory comes from your code (that is not a message Netlify is trying to send to you from our systems). Naively, it seems like your build process is waiting for something that is in this case crashing - yet it doesn’t “respect” the failure correctly, and abort the build process right then. That, you’ll need to fix for yourself in your build pipeline, once we’ve confirmed your suspicions that the error message is correct. This workflow I link below is kind of related to that, and you could use a similar pattern to ensure your build actually exits when it encounters a fatal error, so it doesn’t run for another 40-45 minutes (until your timelimit passes):

4

That one did go over the limits:

Pasted_Image_14_08_22__4_57_PM
Pasted_Image_14_08_22__4_57_PM1868×552 39.2 KB

There was a sharp increase followed by an even sharp decrease as you can see, which would mean that something tried to do something really fast, crashed and then it was all silent.

1 Like
5

Understood. We seen the same issue as well. We’ll try to fix it locally before trying again.

Thank you for your assistance.

1 Like