[Bug]: http2 can cause SIGPIPE on client close

[codebytere]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

master

What operating system are you using?

Ubuntu

Operating System Version

Ubuntu

What arch are you using?

x64

Last Known Working Electron version

11.4.6

Expected Behavior

When I create a http2 server, do nothing, and close it, the child process exits cleanly.

Actual Behavior

The spawned process exits with a null status code as a result of a SIGPIPE.

Testcase Gist URL

https://gist.github.com/codebytere/8a8586d5c58399f23f9398ce763ee218

Additional Information

Caused by nodejs/node#30854 - though what specifically in there i'm not yet sure.

This also only happens on Linux.

[nornagon]

It seems like this is an upstream bug...? Should this be reported against nodejs/node?

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[github-actions]

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.