Bug #6699: rb_barrier_wait() gets blocked when running within a Thread.new { }

• Status: Closed
• Assignee: -
• Target version: 2.0.0
• ruby -v: ruby 2.0.0dev (2012-07-03 trunk 36272) [x86_64-linux]

[ibc (Iñaki Baz Castillo)]

In my Ruby C extension I use rb_barrier_wait(MY_BARRIER) in a method. It works perfectly but I've realized of a case in which it gets
blocked:

Thread.new do
MyExten.my_method
end

In this case the C function rb_barrier_wait(MY_BARRIER) gets blocked (note that I don't call if from other place). So this seems a conflict
of the new Thread and rb_barrier_wait(), it seems that they both try to access to the same shared resource. Is it the expected behavior?

[kosaki (Motohiro KOSAKI)]

Please don't use rb_barrier_wait(). It doesn't have barrier semantics. Moreover, It is not a public API. We might remove it in future release.

[ibc (Iñaki Baz Castillo)]

Thanks for the clarification.

[kosaki (Motohiro KOSAKI)]

• Status changed from Open to Closed