[v2] FATAL ERROR: v8::HandleScope::CreateHandle()

🐛 bug report

Seems like when I try to build it sporadically spits this node error out. There is no rhyme or reason to it afaik.

here is a full output log with the error

.babelrc

{
  "presets": ["@babel/preset-env", "@babel/preset-react"],
  "plugins": [
    [
      "babel-plugin-styled-components",
      {
        "cssProp": true,
        "displayName": true
      }
    ],
    ["@babel/plugin-proposal-class-properties", { "loose": true }],
    ["@babel/plugin-proposal-optional-chaining"]
  ]
}

.parcelrc

{
  "extends": "@parcel/config-default",
  "transformers": {
    "*.{jpg,png,svg}": ["@parcel/transformer-raw"]
  }
}

script.

{"scripts": {
    "build": "parcel build ./src/index.html --dist-dir dist --no-source-maps"
}}

🤔 Expected Behavior

It builds without Exit 134

😯 Current Behavior

Well it actually builds but the error exit with code 134 which causes CI exit code 1 and not continue the deployment.

💁 Possible Solution

Could be something to do with not enough resources?

🔦 Context

This happens on local and ci builds, and local dev. It also happens when i ctrl-c the dev server. It is sporadic.

💻 Code Sample

Sorry all NDA

🌍 Your Environment

Happens on on my i5 4670k with 16gb ram, win 10 Happens in travis on xenial

[pr1ntr]

Seems to be fixed with node 14. I also think it has to do with the size of the build.

[mischnic]

Thanks! Looking at the “n-api” list in https://github.com/nodejs/node/releases/tag/v12.18.3, I’d say it’s https://github.com/nodejs/node/pull/33508? This issue is linked in there: https://github.com/nodejs/node-addon-api/issues/722, it has the exact same error message we are seeing here.

@NordlingDev @pr1ntr does using 12.18.3 fix it for you? In that case, I’d say upgrading Node is a(n) acceptable (“workaround”).

https://github.com/nodejs/node-addon-api/issues/730#issuecomment-636922311:

will most likely be backported to all LTS versions, we should investigate whether we are able to also fix this in node-addon-api, because folks may not necessarily be running the latest of one of the LTS versions