-
Notifications
You must be signed in to change notification settings - Fork 86
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
SIGPIPE on background thread can cause segfault #168
Comments
What!? I could've sworn we sigignored it! |
Need to ignore in later too |
We lost the |
We used to ignore on the main thread, right? We might want to consider just sticking with that (or whatever it is that we used to do), I remember spending a lot of time and energy deciding on the right course of action there. |
We did used to ignore at the process level, each time we were about to do a However, R itself apparently does have a SIGPIPE handler and so I think it would be best not to mess with R's SIGPIPE handling if possible. Somewhat related: s-u/Rserve#100 (comment) |
Originally from rstudio/plumber#289. A SIGPIPE on the httpuv background thread can cause R to segfault.
The text was updated successfully, but these errors were encountered: