New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bytes.copyTo(outputStream) fails #80
Comments
You have provided an example of what does work. Please provide an example of what does NOT work. Thanks. |
Sorry, here a fully reproducible example.
Results in a:
on a: using: BTW, is there a mailing list to discuss these kind things? Amazing library beyond that.... |
I wrote a chaos monkey test having 100 threads writing / reading up to 3GB native memory buffers in parallel. With that, I regularly but not always manage to get the buffer.read method to crash as well. Dump attached. Any help is very appreciated. |
from your log, we see
|
@joa23 I ran your test ( above ) on my iMac, I let it run for a couple of mins, it did not crash, I'm using the latest version of Chronicle-BOM : 2.17.39, please retest with this version an let me know if you still see an issue. |
It's likely that the net.openhft.chronicle.bytes.NativeBytesStore#copyToDirect
I'm not able to reproduce this issue, so are you able to investigate this, perhaps by adding some trace code to record the values just before it crashes. It would be good to see also the (readRemaining() and writeRemaining() What I think is happening here ( but its a guess ) is that either the addr2 is wrong or its copying too much data, in other words, the |
Rob, |
I have added a fix for this, sorry about the long delay. |
Released in Chronicle-Bytes-2.20.43, BOM-2.20.67 |
Released in Chronicle-Bytes-2.20.101, BOM-2.20.134 |
Hi there,
Is there a known issue with bytes.copyTo(outputStream)?
I experience a strange behavior where
bytes.copyTo(outputStream)
stops at 2GB.However simply doing the following works fine:
The text was updated successfully, but these errors were encountered: