The sun.zip.disableMemoryMapping=true property helps with ZipFile class
only. There are other related issues in the ZipInput/Output streams.
Some code areas don't have synchronization and there are opportunities
for the underlying native zip resources to be freed which Java code then
tries to reference causing various SEGV. I've one or two areas of code
identified for tightening up and hope to get to it in coming weeks.
(long standing action item)
So we catch the signal, right? Maybe there's something I'm missing...
We don't catch/detect such SEGV's. Would it make sense, is it possible ?
regards,
Sean.
On 27/02/2015 09:34, Andrew Haley wrote:
On 26/02/15 22:17, Christos Zoulas wrote:
There are numerous bug reports about the jvm crashing in libzip...
Just google for "libzip java crash". The bottom line is that using
mmap is problematic (I can get into more per OS details if necessary)
because it will potentially signal when the file size is altered.
So we catch the signal, right? Maybe there's something I'm missing...
Andrew.
