Skip to content

Segmentation fault (core dumped) after all workers are done #186

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

Open
patrou opened this issue Jun 15, 2018 · 0 comments
Open

Segmentation fault (core dumped) after all workers are done #186

patrou opened this issue Jun 15, 2018 · 0 comments

Comments

@patrou
Copy link

patrou commented Jun 15, 2018

Hello,

I am writing a script in which I spawn n workers, I assign them a task, when they finish they post a message with the result and they are done. When all threads are done, a callback is returned to continue with the main execution of the program.

The above code produces Segmentation fault (core dumped). It happens very rarely in the end of the program after all results are collected and printed in the main thread. In a VM environment, it happened 6/5040 times. In other platforms happens with different ratio or never.

I, also used the --trace_gc flag. But, I noticed that Segmentation fault can be caused with or without any flags.

Any suggestion will be helpful.

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

No branches or pull requests

1 participant