rubinius/rubinius — Issue #1386: Spurious crash during CI runs
Author: dbussink
Created: 2011-10-29 15:01:15+00:00
State: open

The backtraces, crash and thread information can be found here:

https://gist.github.com/e8c1247fa5e7b2d01b02

What I'm wondering is whether this is actually a problematic state we're in. What happened is that a thread is signaled to wake up and right after that a stop the world is requested for GC. The thread that has been woken up is marked as suspended due to the stop the world, but also tries to unlock the contention lock.

Because the contention lock is now also a GC lock guard, it then sees that the thread is already suspended because of the GC stop the world and subsequently crashes like this.