title: chronicle-bytes raising a segfault
body: <p>following the accepted solution in <a href="https://stackoverflow.com/questions/52848025/chronicle-bytes-shared-directbytesstores">chronicle-bytes shared DirectBytesStores</a> I have now set up my code in the same way to the accepted answer.</p>
  
  <p>I'm generating 1,000,000 objects that I write out to a MappedFile and I would like each object to be able to manage their own reads/writes to the MappedFile:</p>
  
  <pre><code>public class DataObject {
  
      public static final int LENGTH = 12;
      private static final int A_OFFSET = 0;
      private static final int B_OFFSET = 4;
  
      private PointerBytesStore bytes;
  
      public DataObject(long memoryAddress) {
          this.bytes = new PointerBytesStore();
          this.bytes.set(memoryAddress, LENGTH)
      }
  
      public int getA() {
          return this.bytes.readInt(A_OFFSET);
      }
  
      public void setA(int a) {
          this.bytes.writeInt(a);
      }
  
      ...
  }
  </code></pre>
  
  <p>Then I create DataObject with:</p>
  
  <pre><code>MappedFile file = MappedFile.mappedFile(new File(tmpfile), 64 &lt;&lt; 10);
  MappedBytes mappedBytes = MappedBytes.mappedBytes(mappedFile);
  int offset = 0;
  List&lt;DataObject&gt; myList = new ArrayList&lt;&gt;();
  for(i = 0; i &lt; 1000000; i++) {
      int address = mappedBytes.addressForRead(offset);
      myList.add(new DataObject(address));
      offset += DataObject.LENGTH;
  }
  </code></pre>
  
  <p>I have found, using code similar to above, that chronicle-bytes generates a segfault once I reach ~100,000 objects. The segfault tends to happen when trying to read or write to the PointerBytesStore but is not predictable.</p>
  
  <p>Is this a bug in chronicle-bytes or is am I misusing the library? Any help/suggestions/recommendations would be greatly appreciated.</p>