Skip to content
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

Two consecutive signals crash block until next timeout #455

Open
nfraprado opened this issue Oct 17, 2021 · 1 comment · May be fixed by #454
Open

Two consecutive signals crash block until next timeout #455

nfraprado opened this issue Oct 17, 2021 · 1 comment · May be fixed by #454

Comments

@nfraprado
Copy link

When a signal is sent to update a block, and while the block's process is running another signal is sent, the block's process crashes, so it disappears and doesn't get updated again until the next signal is sent or timeout reached.

I finally tracked this bug down and fixed it in #454.

PS: I can't overstate how happy I am to finally track down this bug after more than a year of being bothered by it. Hope this helps others as well :).

@vivien
Copy link
Owner

vivien commented Dec 28, 2022

Hi @nfraprado! Thanks for going down this rabbit hole! Unfortunately I'm not able to reproduce the issue on my side. Do you have a minimal example to reproduce this?

vivien added a commit that referenced this issue Jan 13, 2023
Now that the original signal mask from the parent process is stored
in bar->sigset, use it to restore the signal set in child processes
instead of unblocking them all.

Refs #454
Closes #455
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 a pull request may close this issue.

2 participants