Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
legroen opened this issue May 8, 2018 · 1 comment

Comments

@legroen
Copy link

legroen commented May 8, 2018

Please, provide the details below:

Did you verify this is a real problem by searching the [NativeScript Forum]

I have a 64bit system with 16GB of mem. I've tried various suggestions, i've added following to my env.

JAVA_OPTS=-Xms4096m -Xmx8192m

Tell us about the problem

JavaScript heap out of memory when running tns run android immediately after tns create test --ng

Which platform(s) does your issue occur on?

Windows 10 Pro 64 bit

Please provide the following version numbers that your issue occurs with:

  • CLI: (run tns --version to fetch it)
    4.0.0
  • Cross-platform modules: (check the 'version' attribute in the
    node_modules/tns-core-modules/package.json file in your project)
    4.0.0
  • Runtime(s): (look for the "tns-android" and "tns-ios" properties in the
    package.json file of your project)
    4.0.1
  • Plugin(s): (look for the version number in the package.json file of your
    project)

Please tell us how to recreate the issue in as much detail as possible.

tns create test --ng
cd test
tns run android

@legroen
Copy link
Author

legroen commented May 8, 2018

OK, this is solved.

I installed nativescript with sidekick, everything went (no errors or none that I saw).

My colleague did the same thing (install with sidekick), downloaded the same tutorial app and everything worked.

The solutions mentioned in here e.g. changing --max_old_space_size=4096 to 2000 or something other is an option of node.js.

After checking the version of node.js of my colleague we saw that he had 8.1.0 and that I had 6.10.3.
with the following tool you can list the available node.js version and there arch.

Mine was 6.10.3 with 32-bit arch.

I installed 8.11.1 - 64 bit arch and my issue disappeared.

In my search I came across posts about a 1.9GB limit somewhere, so I guess my issue had something to do with 32/64 bit env.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants