First 2 elements of ringBuffer are null about disruptor-net HOT 7 CLOSED

Downloading the source code, and investigating, within RingBuffer.Fill, there's a variable called _bufferPadRef which is used to leave some nulls at the start of the ringBuffer.

If I create new ringbuffer entries for those initial entries which are meant to be ununused (in the buffer), then my code will run on Linux too without any problems.

That's a fudge, clearly the padding is there for a reason.

from disruptor-net.

I see the problem: in the Util class, the array data offset is assumed to be 8/16 bytes but this is not the case on Mono. I will fix that, sorry.

from disruptor-net.

great - can you let me know when it's released please?

from disruptor-net.

Sure. The data offset code was only changed in the last version, you can try using version 3.6.0 if you want to.

from disruptor-net.

I just pushed a fix, can you try it before I publish the package?

from disruptor-net.

I was able to run the tests and the performance tests on Mono-x32 and Mono-x64, so I published a new version with the fix.

from disruptor-net.

sorry, would have done this for you, but we're clearly in different timezones.
I've just tested the release, looks good to me, thanks.

from disruptor-net.