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

Seg fault in hpx::serialization::output_archive::add_gid when running octotiger #1920

Closed
dmarce1 opened this issue Dec 20, 2015 · 6 comments

Comments

Projects
None yet
3 participants
@dmarce1
Copy link
Member

commented Dec 20, 2015

I got a seg fault in hpx::serialization::output_archive::add_gid when running octotiger.

The full output is here:

https://gist.github.com/dmarce1/c1cfef5458857f7d7029

Most of the time I run the code, the future on line 231 of node_octstruct.cpp or the future on line 470 of node_server.cpp times out - the seg fault here is at the same stage in execution as the former, maybe the two are related.

This is with Octotiger dmarce1/octotiger@049ee7e and HPX ac9c127 (the latest HPX commit that I can compile without an Intel 15 bug popping up)

@hkaiser hkaiser added this to the 0.9.12 milestone Dec 20, 2015

@hkaiser

This comment has been minimized.

Copy link
Member

commented Dec 20, 2015

Looks like a race

@sithhell

This comment has been minimized.

Copy link
Member

commented Dec 21, 2015

I think it's a stack overflow, can you try to run with a larger stack size?

@hkaiser

This comment has been minimized.

Copy link
Member

commented Dec 21, 2015

@sithhell Do we still run serialization on a separate thread? If yes, we might want to increase the stack size for those by default.

@dmarce1

This comment has been minimized.

Copy link
Member Author

commented Dec 21, 2015

Running with larger stack sizes seems to fix the problem. Though I've only gone for a couple hundred timesteps. I will wait to close the issue until its run further.

@dmarce1 dmarce1 closed this Dec 21, 2015

@hkaiser

This comment has been minimized.

Copy link
Member

commented Dec 21, 2015

How much larger have you gone?

@hkaiser

This comment has been minimized.

Copy link
Member

commented Dec 23, 2015

@dmarce1 how large did you make the stack for your application to run?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.