rubinius/rubinius — Issue #1296: Threading in 2.0.testing branch segfaults with Rinda
Author: jmstacey
Created: 2011-10-19 06:13:52+00:00
State: open

Garbage collection seems to be causing segfaults when Rinda is involved. This appears to be related to an issue that I filed last year and was resolved: https://github.com/rubinius/rubinius/issues/631

Here is one crash report: http://pastebin.com/YwMAjzLx

My current code that is reproducing this problem is a distributed prime number generator which makes use of Ring and Tuplespace within Rinda. I can share the code if wanted, but it's several hundred lines and requires a bit of setup to run [just fair warning]. However, because it's long running it will reliably reproduce the error, so let me know on that.

Running the code in gdb provides the following additional information:

```
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x00000001058f9000
[Switching to process 96854 thread 0x200b]
0x00000001001d11f0 in rubinius::CompiledMethod::stack_size () at /Users/jon/Desktop/rubinius/vm/builtin/compiledmethod.hpp:25
25 return STRIP_FIXNUM_TAG(this);
```

Here's the full backtrace from gdb: http://pastebin.com/kWSL8fPt