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

Unable to compile core-js using node 18+ #654

Open
MomboteQ opened this issue Jul 10, 2024 · 3 comments
Open

Unable to compile core-js using node 18+ #654

MomboteQ opened this issue Jul 10, 2024 · 3 comments

Comments

@MomboteQ
Copy link

New issue checklist

General information

  • Library version(s): latest
  • Browser version(s): -
  • Devices/Simulators/Machine affected: -
  • Reproducible in the testnet? (Yes/No): -
  • Related issues: -

Bug report

Crash log? Screenshots? Videos? Sample project?

(...)
[17:02:56] Finished 'run-build-web-babel' after 42 s

<--- Last few GCs --->

[5689:0x4ca7c00]    69776 ms: Mark-sweep 981.7 (1041.0) -> 973.8 (1041.2) MB, 439.9 / 0.0 ms  (average mu = 0.108, current mu = 0.029) allocation failure scavenge might not succeed
[5689:0x4ca7c00]    70278 ms: Mark-sweep 982.0 (1041.2) -> 974.1 (1041.5) MB, 494.8 / 0.0 ms  (average mu = 0.062, current mu = 0.016) allocation failure scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb090e0 node::Abort() [gulp build]
 2: 0xa1b70e  [gulp build]
 3: 0xce1a20 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [gulp build]
 4: 0xce1dc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [gulp build]
 5: 0xe99435  [gulp build]
 6: 0xe99f16  [gulp build]
 7: 0xea843e  [gulp build]
 8: 0xea8e80 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [gulp build]
 9: 0xeabdfe v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [gulp build]
10: 0xe6d33a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [gulp build]
11: 0x11e61e6 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [gulp build]
12: 0x15d9e59  [gulp build]
Aborted (core dumped)
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@sisou
Copy link
Member

sisou commented Jul 11, 2024

Hi there! A quick scan shows me "out of memory" error. How much free RAM do you have when you start this command?

@MomboteQ
Copy link
Author

1gb

@sisou
Copy link
Member

sisou commented Jul 12, 2024

I just ran it on my machine and it used a max of 12% of my 15GB, so that's 1.8GB. So I'd say you need at least 2 GB free RAM to run the main build command, which builds everything in parallel.

You can choose to only build certain tasks, by running yarn gulp <task name>, where <task name> can be any of the tasks defined in the gulpfile, e.g. build-web to only build browser files:
https://github.com/nimiq/core-js/blob/master/gulpfile.js#L632

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