Only thing I can see from looking at the exception, is that it looks like - I didn’t disassemble the code from hex - that the “peer” value in the RefCountedMemory object is probably 0
Given that Unsafe.allocateMemory should not return 0 even on allocation failure (which should throw OOM) - though you should add a log statement to the Memory class to check that - I’d suggest logging to see if anyone is calling SSTableReader.releaseSummary, which could set the peer to 0 > On Nov 17, 2014, at 7:30 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > > On 11/17/2014 07:19 PM, William Arbaugh wrote: >> I've successfully built 2.1.2 for FreeBSD, but the JVM crashes upon start-up. >> >> Here's the snippet from the top of the log file (attached) >> >> # >> # A fatal error has been detected by the Java Runtime Environment: >> # >> # SIGSEGV (0xb) at pc=0x0000000802422655, pid=76732, tid=34384931840 >> # >> >> Any hints on how to get 2.1.2 working on FreeBSD is appreciated. >> > > Not a very helpful hint, other than the fact you are not alone :) > > https://issues.apache.org/jira/browse/CASSANDRA-8325 > > -- > Michael
smime.p7s
Description: S/MIME cryptographic signature
