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

Using thread_pool_executors causes segfault #1112

Closed
hkaiser opened this issue Apr 9, 2014 · 2 comments
Closed

Using thread_pool_executors causes segfault #1112

hkaiser opened this issue Apr 9, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@hkaiser
Copy link
Member

hkaiser commented Apr 9, 2014

Using the thread_pool_executor class causes a segmentation fault if it is used with more than one core.

@hkaiser hkaiser added this to the 0.9.9 milestone Apr 9, 2014
@hkaiser hkaiser self-assigned this Apr 9, 2014
@sithhell sithhell modified the milestones: 0.9.10, 0.9.9 Mar 10, 2015
@sithhell
Copy link
Member

The test covering this issue is still occasionally segfaulting. See for example here:
http://hermione.cct.lsu.edu/builders/hpx_gcc_4_7_boost_1_51_debian_x86_64_debug/builds/295/steps/run_regression_tests/logs/stdio

From a quick look at the failure, it looks like the segfault is caused when trying to execute one of the registered shutdown functions. I don't know why this happens.

@sithhell sithhell reopened this Mar 10, 2015
@hkaiser hkaiser modified the milestones: 0.9.11, 0.9.10 Mar 19, 2015
@hkaiser
Copy link
Member Author

hkaiser commented May 31, 2015

This has been fixed by 48565b9

@hkaiser hkaiser closed this as completed May 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants