Skip to content

win: fix leak processing fs event#4656

Merged
saghul merged 1 commit intov1.xfrom
win-fsevent-leak
Dec 16, 2024
Merged

win: fix leak processing fs event#4656
saghul merged 1 commit intov1.xfrom
win-fsevent-leak

Conversation

@saghul
Copy link
Copy Markdown
Member

@saghul saghul commented Dec 16, 2024

Copy link
Copy Markdown
Member

@santigimeno santigimeno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed this. Thanks for taking care of it

@saghul saghul merged commit ec5a4b5 into v1.x Dec 16, 2024
@saghul saghul deleted the win-fsevent-leak branch December 16, 2024 12:58
@saghul
Copy link
Copy Markdown
Member Author

saghul commented Dec 16, 2024

👍 the function is quite involved, it's easy to miss! I also had to look twice 😅

@kingyue737
Copy link
Copy Markdown

Sorry for bothering you. Could we release a version with this fix? This issue results in severe memory leaks for Nuxt users on Windows nuxt/devtools#761 nuxt/cli#628. Since It might take more than a month until node picks the upgrade of libuv, it would be nice if a patch for libuv is released before the next node release.

@saghul
Copy link
Copy Markdown
Member Author

saghul commented Jan 10, 2025

Node does apply fixes to the vendored libuv they have. If this is Bad (TM) I'd suggest you open an issue in Node and ask for a cherry-pick.

That said, a release is due IMHO!

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

Successfully merging this pull request may close these issues.

3 participants