On Fri, 19 May 2023 06:58:49 GMT, Matthias Baesken <mbaes...@openjdk.org> wrote:
> MappedMemoryUtils.c can generate exceptions like those : > java.io.UncheckedIOException: java.io.IOException: Invalid argument > at > java.base/java.nio.MappedMemoryUtils.force(MappedMemoryUtils.java:105) > at java.base/java.nio.Buffer$2.force(Buffer.java:890) > at > java.base/jdk.internal.misc.ScopedMemoryAccess.forceInternal(ScopedMemoryAccess.java:317) > at > java.base/jdk.internal.misc.ScopedMemoryAccess.force(ScopedMemoryAccess.java:305) > at > java.base/jdk.internal.foreign.MappedMemorySegmentImpl.force(MappedMemorySegmentImpl.java:92) > at > TestByteBuffer.testMappedSegmentAsByteBuffer(TestByteBuffer.java:327) > > (we see this for example on AIX); there is some room for improvement, at > least the info should be added that msync failed and caused this exception. Hi Alan, thanks for the comments. I changed the exception texts regarding madvise and adjusted the Java-comments ------------- PR Comment: https://git.openjdk.org/jdk/pull/14054#issuecomment-1554314469