You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You will notice that the child never dies. It will hang forever in the task manager. If instead of SEA you use plain node scripts (and modify parent.js to spawn node child.js) it works as expected.
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
The child process to exit
What do you see instead?
It hangs forever
Additional information
No response
The text was updated successfully, but these errors were encountered:
PS: I have this workaround that works, which follows the nodejs internalities when creating the stdin, but still createReadStream is the way to go I guess as this workaround is not a public API. Still feels weird that createReadStream in non-sea works and sea doesn't.
Version
22.14 and 23.10
Platform
What steps will reproduce the bug?
Create 2 files:
Create a SEA binary from child.js:
Now run
parent.js
You will notice that the child never dies. It will hang forever in the task manager. If instead of SEA you use plain node scripts (and modify
parent.js
tospawn node child.js
) it works as expected.How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
The child process to exit
What do you see instead?
It hangs forever
Additional information
No response
The text was updated successfully, but these errors were encountered: