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

Nx serve broken with Node v23.0.0 #28516

Closed
1 of 4 tasks
mathijshenquet opened this issue Oct 18, 2024 · 2 comments
Closed
1 of 4 tasks

Nx serve broken with Node v23.0.0 #28516

mathijshenquet opened this issue Oct 18, 2024 · 2 comments

Comments

@mathijshenquet
Copy link

mathijshenquet commented Oct 18, 2024

Current Behavior

I get these kind of error traces when runing nx run {my-app}:serve

<--- Last few GCs --->

[16752:00000232A3E68000]    38855 ms: Scavenge (interleaved) 4082.0 (4091.2) -> 4076.7 (4092.7) MB, pooled: 0 MB, 5.85 / 0.00 ms  (average mu = 0.223, current mu = 0.211) allocation failure;
[16752:00000232A3E68000]    41129 ms: Mark-Compact (reduce) 4076.9 (4092.7) -> 4076.8 (4079.2) MB, pooled: 0 MB, 1882.88 / 0.00 ms  (+ 1.9 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1888 ms) (average mu = 0.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 00007FF6810E25DB node::SetCppgcReference+15707
 2: 00007FF68104B7F8 DSA_meth_get_flags+98136
 3: 00007FF681D4CF71 v8::Isolate::ReportExternalAllocationLimitReached+65
 4: 00007FF681D397B6 v8::Function::Experimental_IsNopFunction+2710
 5: 00007FF681B70680 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+34016
 6: 00007FF681B6997D v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+6109
 7: 00007FF681B6589D v8::Platform::SystemClockTimeMillis+655213
 8: 00007FF681380D1D BIO_ssl_shutdown+189
 9: 00007FF681B6D214 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+20596
10: 00007FF681BD1F1A v8::Locker::IsLocked+7338
11: 00007FF68183CBD0 v8::internal::Version::GetString+451664
12: 00007FF621DF027A

Downgrading to e.g. node 20 solves the problem.

Expected Behavior

Does not crash

GitHub Repo

No response

Steps to Reproduce

Run nx run {app}:server

Nx Report

Node           : 23.0.0
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 10.2.4

nx (global)        : 19.8.6
nx                 : 19.8.6
@nx/js             : 19.8.6
@nx/linter         : 19.8.6
@nx/eslint         : 19.8.6
@nx/workspace      : 19.8.6
@nx/cypress        : 19.8.6
@nx/devkit         : 19.8.6
@nx/eslint-plugin  : 19.8.6
@nx/react          : 19.8.6
@nrwl/tao          : 19.8.6
@nx/vite           : 19.8.6
@nx/web            : 19.8.6
typescript         : 5.5.4
---------------------------------------
Registered Plugins:
@nx/vite/plugin
@nx/eslint/plugin
@nx/cypress/plugin

Failure Logs

<--- Last few GCs --->

[29328:0000026AE1B81000]    35255 ms: Scavenge (interleaved) 4081.4 (4090.7) -> 4076.2 (4092.0) MB, pooled: 0 MB, 5.30 / 0.00 ms  (average mu = 0.175, current mu = 0.149) allocation failure;
[29328:0000026AE1B81000]    37529 ms: Mark-Compact (reduce) 4076.3 (4092.0) -> 4076.2 (4078.5) MB, pooled: 0 MB, 1948.11 / 0.00 ms  (+ 1.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1953 ms) (average mu = 0.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
> nx run sky-web-app:serve


<--- Last few GCs --->

[29328:0000026AE1B81000]    35255 ms: Scavenge (interleaved) 4081.4 (4090.7) -> 4076.2 (4092.0) MB, pooled: 0 MB, 5.30 / 0.00 ms  (average mu = 0.175, current mu = 0.149) allocation failure;
[29328:0000026AE1B81000]    37529 ms: Mark-Compact (reduce) 4076.3 (4092.0) -> 4076.2 (4078.5) MB, pooled: 0 MB, 1948.11 / 0.00 ms  (+ 1.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1953 ms) (average mu = 0.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

<--- Last few GCs --->

[29328:0000026AE1B81000]    35255 ms: Scavenge (interleaved) 4081.4 (4090.7) -> 4076.2 (4092.0) MB, pooled: 0 MB, 5.30 / 0.00 ms  (average mu = 0.175, current mu = 0.149) allocation failure;
[29328:0000026AE1B81000]    37529 ms: Mark-Compact (reduce) 4076.3 (4092.0) -> 4076.2 (4078.5) MB, pooled: 0 MB, 1948.11 / 0.00 ms  (+ 1.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1953 ms) (average mu = 0.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

[29328:0000026AE1B81000]    35255 ms: Scavenge (interleaved) 4081.4 (4090.7) -> 4076.2 (4092.0) MB, pooled: 0 MB, 5.30 / 0.00 ms  (average mu = 0.175, current mu = 0.149) allocation failure;
[29328:0000026AE1B81000]    37529 ms: Mark-Compact (reduce) 4076.3 (4092.0) -> 4076.2 (4078.5) MB, pooled: 0 MB, 1948.11 / 0.00 ms  (+ 1.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1953 ms) (average mu = 0.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
t mu = 0.149) allocation failure;
[29328:0000026AE1B81000]    37529 ms: Mark-Compact (reduce) 4076.3 (4092.0) -> 4076.2 (4078.5) MB, pooled: 0 MB, 1948.11 / 0.00 ms  (+ 1.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1953 ms) (average mu = 0.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

----- Native stack trace -----

 1: 00007FF6810E25DB node::SetCppgcReference+15707
 2: 00007FF68104B7F8 DSA_meth_get_flags+98136
 3: 00007FF681D4CF71 v8::Isolate::ReportExternalAllocationLimitReached+65
 4: 00007FF681D397B6 v8::Function::Experimental_IsNopFunction+2710
 5: 00007FF681B70680 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+34016
 6: 00007FF681B6997D v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+6109
 7: 00007FF681B6589D v8::Platform::SystemClockTimeMillis+655213
 8: 00007FF681380D1D BIO_ssl_shutdown+189
 9: 00007FF681B6D214 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+20596
10: 00007FF681BD1F1A v8::Locker::IsLocked+7338
11: 00007FF68183CBD0 v8::internal::Version::GetString+451664
12: 00007FF621DF027A

Package Manager Version

npm 10.2.4

Operating System

  • macOS
  • Linux
  • Windows
  • Other (Please specify)

Additional Information

Sorry for not giving a reproduction code, I don't expect a fix I just wanted to flag that this is happening here. I would be willing to generate reproduction code if the nx maintainers consider this valuable.

@jaysoo
Copy link
Member

jaysoo commented Oct 25, 2024

Hi @mathijshenquet , we don't officially support odd Node versions since they are not stable (only the even releases make it into LTS).

If you try Node 20 or 22 then there shouldn't be any problems.

@jaysoo jaysoo closed this as completed Oct 25, 2024
Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants