node version: 8.10.0
npm -v: 5.6.0
system: mac
on running npm run build, system throws following error
67% building modules 2081/2181 modules 100 active
...ent/completed-shipment.component.scssng(85928,0x70000312e000)
malloc: *** error for object 0x1023e9fd0: pointer being freed was not
allocated
Clearly this is because of css and probably related to variables/functions in css. But not sure where the issue lies. This was working clean 2 days earlier but started to fail now. Any known issues recently on node-sass/libsass?
Related
Even before any test execution, I've run into a problem. My Cypress Test Runner is stuck on the very beginning, and has infinite loading.
Have tried reinstalling, but still the same.
I am using MacOS Big Sur, and this is what comes up when I type cypress --version
Cypress package version: 9.2.0
Cypress binary version: 9.2.0
Electron version: 15.2.0
Bundled Node version: 16.5.0
I've also tried DEBUG=cypress:* ./node_modules/.bin/cypress open, and I get the following:
current & mean memory and CPU usage by process group:
and then table with contents, which repeats every ~10sec.
Has anyone else encountered this issue?
Found an issue, the node version was 17, and for some reason I got the error --openssl-legacy-provider is not allowed in NODE_OPTIONS
After I changed the node version to 16.x it works.
When trying to deploy my application with Serverless Framework using the properties:
package:
individually: true
i got the follow error:
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
My NodeJS version is 10..
Some people said to enhance the NodeJS memory with the code:
export NODE_OPTIONS="--max-old-space-size=8192"
But i had no happy result.
I just ended up this error installing a newer version of NodeJS. In my case v14.15.4
I really need some help with what seems to be the most basic task (setting up the expo/react-native project). I've installed the expo-cli (v3.11.7), react-native (v2.0.1), watchman (v4.9.0) and node (v12.14.1). I've followed the tutorial up until the point where I need to run expo start and I get the following error:
Your project is in SDK version >= 33.0.0, but the expo package version seems to be older.
Error: node_modules directory is missing. Please run npm install in your project directory.
Couldn't start project. Please fix the errors and restart the project.
Set EXPO_DEBUG=true in your env to view the stack trace.
I've then run npm install and tried again but the same error pops up. I've removed the node_modules folder and that didn't work either.
Update:
When I npm install this is the error I'm seeing:
npm WARN deprecated core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm ERR! code EPROTO
npm ERR! errno EPROTO
npm ERR! request to https://codeload.github.com/expo/react-native/tar.gz/sdk-36.0.0 failed, reason: write EPROTO 4521895360:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40
I've installed yarn (v1.21.1) and tried installing using this with the same error:
warning expo > fbemitter > fbjs > core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
error An unexpected error occurred: "https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz: write EPROTO 4356277696:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40
Can anyone advise?
I've managed to solve the problem. I was trying to install over my home network, which apparently has some proxy restrictions! No idea why.
Someone advised me to try again but connected to another network or my mobile hotspot. I tried this and it worked! Problem solved. So I guess for any others that may be experiencing the same problem, try connecting to another network and see if that helps.
If this fails, then I suppose looking at the proxy configuration and making changes there may help. But I wouldn't advise doing this unless you know exactly what you're doing.
Getting the following message when trying to build for android
Processing node_modules failed. Error: spawn ENAMETOOLONG
nativescript 2.4 and android 2.4.1 - all updated.
npm version 3.10.8
node 6.9.1
also using SCSS
I googled and looks like it has to do with windows command line limit.
I'm running Fedora 9 x86_64 and am more or less a Linux newbie (not using it, but installing and such). The error occurs in the second stage of the bootstrap (i.e. "./bootstrap_stage2").
It does a whole lot fo stuff and then these errors start happening:
Fatal error: exception Out_of_memory
make[8]: *** [odoc_html.cmo] Error 2
make[8]: Leaving directory `/home/matthew/godi/build/godi/godi-ocaml/work/ocaml/ocamldoc'
make[7]: *** [ocamldoc] Error 2
make[7]: Leaving directory `/home/matthew/godi/build/godi/godi-ocaml/work/ocaml'
Error: Exec error: File /home/matthew/godi/build/godi/godi-ocaml/./../../mk/bsd.pkg.mk, line 1039: Command returned with non-zero exit code
Error: Exec error: File /home/matthew/godi/build/godi/godi-ocaml/./../../mk/bsd.pkg.mk, line 1378: Command returned with non-zero exit code
Error: Command fails with code 1: godi_console
Failure!
I've run it monitoring my memory and can say that I definately have not run out (using about 500 and I've got 3).
So anyone know what the issue is? I've searched the net, but the only other similar thing I found was the other thread on here (but it had a different error)
Any help would be much appreciated, because last time I installed it, it worked flawlessly.
This looks like a known problem with old OCaml (<3.11) on 64-bit platforms likely triggered by heap randomization, which is enabled on Fedora. It's been fixed so far as I know in recent releases (3.11 at least, possibly 3.10.2). Up-to-date GODI running out of section 3.11 should work if this is the case.