-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
process.stdout may memleak if write file failed. #47948
Comments
killagu
added a commit
to killagu/node
that referenced
this issue
May 10, 2023
killagu
added a commit
to killagu/node
that referenced
this issue
May 10, 2023
killagu
added a commit
to killagu/node
that referenced
this issue
May 10, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
tniessen
changed the title
processs.stdout may memleak if write file failed.
process.stdout may memleak if write file failed.
May 10, 2023
killagu
added a commit
to killagu/node
that referenced
this issue
May 11, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
killagu
added a commit
to killagu/node
that referenced
this issue
May 11, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
killagu
added a commit
to killagu/node
that referenced
this issue
May 14, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
killagu
added a commit
to killagu/node
that referenced
this issue
May 14, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
killagu
added a commit
to killagu/node
that referenced
this issue
Jun 26, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
killagu
added a commit
to killagu/node
that referenced
this issue
Jun 26, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948
killagu
added a commit
to killagu/node
that referenced
this issue
Jun 26, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948 Signed-off-by: killagu <[email protected]>
nodejs-github-bot
pushed a commit
that referenced
this issue
Jun 26, 2023
Catch SyncWriteStream write file error. Fixes: #47948 Signed-off-by: killagu <[email protected]> PR-URL: #47949 Reviewed-By: Luigi Pinca <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Jul 3, 2023
Catch SyncWriteStream write file error. Fixes: #47948 Signed-off-by: killagu <[email protected]> PR-URL: #47949 Reviewed-By: Luigi Pinca <[email protected]>
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Aug 14, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948 Signed-off-by: killagu <[email protected]> PR-URL: nodejs#47949 Reviewed-By: Luigi Pinca <[email protected]>
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Aug 14, 2023
Catch SyncWriteStream write file error. Fixes: nodejs#47948 Signed-off-by: killagu <[email protected]> PR-URL: nodejs#47949 Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno
pushed a commit
that referenced
this issue
Sep 10, 2023
Catch SyncWriteStream write file error. Fixes: #47948 Signed-off-by: killagu <[email protected]> PR-URL: #47949 Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno
pushed a commit
that referenced
this issue
Sep 13, 2023
Catch SyncWriteStream write file error. Fixes: #47948 Signed-off-by: killagu <[email protected]> PR-URL: #47949 Reviewed-By: Luigi Pinca <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Platform
Linux::5.15.49-linuxkit
Subsystem
fs
What steps will reproduce the bug?
Create a container with disk size is 1m.
Create a file named test.js.
Run it and rotate stdout to a file in the tmpfs.
node test.js > /run/test.log
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
It's the memory leak.
Additional information
No response
The text was updated successfully, but these errors were encountered: