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

Crash in wait, on macOS #138

Closed
gaborcsardi opened this Issue Jul 22, 2018 · 4 comments

Comments

Projects
None yet
1 participant
@gaborcsardi
Member

gaborcsardi commented Jul 22, 2018

E.g. https://travis-ci.org/r-lib/processx/jobs/406825805

Seems like a race condition when a finalizer or a SIGCHILD handler (?) is called while waiting.

@gaborcsardi gaborcsardi added this to the 3.2.0 milestone Jul 22, 2018

@gaborcsardi

This comment has been minimized.

Member

gaborcsardi commented Jul 22, 2018

This helps: https://travis-ci.org/r-lib/processx/jobs/406887924

It seems that the sigchld arrives in the middle of the polling, which should be OK in general, but seemingly it is not?

@gaborcsardi

This comment has been minimized.

Member

gaborcsardi commented Jul 22, 2018

Some modes of failure:

sigchld remove  8525
[1] "call to wait"
wait
handle active
setup sigchld
block sigchld after setting up
polling
sigchld remove  8526
polling
[1] "1"
 *** caught segfault ***
address 0xffffffff8b023d68, cause 'memory not mapped'
sigchld remove  6727
sigchld remove  6728
sigchld remove  6729
sigchld remove  6730
 *** caught segfault ***
address 0xffffffffb2ae0a00, cause 'memory not mapped'

The first one seems to be more frequent...

@gaborcsardi

This comment has been minimized.

Member

gaborcsardi commented Jul 22, 2018

This was the first time it happened: https://travis-ci.org/r-lib/processx/jobs/389200807

@gaborcsardi

This comment has been minimized.

Member

gaborcsardi commented Jul 23, 2018

Fixed by #142.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment