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

Possible race condition in core.thread (at least on FreeBSD/x86_64 and Linux/PPC64) #495

Open
redstar opened this issue Oct 9, 2013 · 1 comment

Comments

@redstar
Copy link
Member

redstar commented Oct 9, 2013

On FreeBSD/x86_64 and Linux/PPC64, the test "Multiple threads running shared fibers" of module core.thread segfaults.

The observed behaviour is:

  • the threads are created but they don't start
  • the main thread calls joinAll
  • the first thread starts
  • a fiber context switch is initiated

=> boom!

The segfault vanishes if you change the timings, e.g. insert a `printf´ into the thread delegate.

This does not happen on Linux/x86 and Linux/x86_64. Therefore it is unclear if it is a race condition in the unit test or a code generation bug.

The crash on OS X reported in issue #492 might have the same root cause.

@redstar
Copy link
Member Author

redstar commented Jan 26, 2014

Same failure on mingw32 with release 0.13.0. Requires compiling with at least -O2.

redstar pushed a commit that referenced this issue Sep 27, 2014
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