-
-
Notifications
You must be signed in to change notification settings - Fork 35.7k
Potential regression with libuv in Node 24.16.0 #63638
Copy link
Copy link
Open
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.
Description
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Version
24.16.0
Platform
Subsystem
Microsoft Windows Server 2025 10.0.26100 (GitHub Actions runner)
What steps will reproduce the bug?
Run Puppeteer test suites with Node 24.16.0 https://github.com/puppeteer/puppeteer/actions/runs/26626414041/job/78464147790#step:11:505
How often does it reproduce? Is there a required condition?
It is flaky but happens noticeably in our test CI
https://github.com/puppeteer/puppeteer/actions/runs/26626414041/job/78464147790#step:11:505
https://github.com/puppeteer/puppeteer/actions/runs/26626414041/job/78464147790#step:11:505
https://github.com/puppeteer/puppeteer/actions/runs/26626414041/job/78464147915#step:11:487
3 failures in a single run.
What is the expected behavior? Why is that the expected behavior?
No crahes.
What do you see instead?
Node exists with
Assertion failed: !_wcsnicmp(filename, dir, dirlen), file src\win\fs-event.c, line 72Additional information
Downgrading to Node 24.15.0 seems to have helped. Possibly related to libuv/libuv#5010