Author: tilman
Date: Sun Nov 9 13:37:22 2025
New Revision: 1929613
Log:
PDFBOX-5660: improve javadoc, as suggested by Valery Bokov; closes #319
Modified:
pdfbox/trunk/io/src/main/java/org/apache/pdfbox/io/IOUtils.java
Modified: pdfbox/trunk/io/src/main/java/org/apache/pdfbox/io/IOUtils.java
==============================================================================
--- pdfbox/trunk/io/src/main/java/org/apache/pdfbox/io/IOUtils.java Sun Nov
9 13:37:12 2025 (r1929612)
+++ pdfbox/trunk/io/src/main/java/org/apache/pdfbox/io/IOUtils.java Sun Nov
9 13:37:22 2025 (r1929613)
@@ -167,11 +167,13 @@ public final class IOUtils
}
/**
- * Unmap memory mapped byte buffers. This is a hack waiting for a proper
JVM provided solution expected in java 10
- * https://bugs.openjdk.java.net/browse/JDK-4724038 The issue here is that
even when closed, memory mapped byte
- * buffers hold a lock on the underlying file until GC is executes and
this in turns result in an error if the user
- * tries to move or delete the file.
- *
+ * Unmap memory mapped byte buffers. This is a hack waiting for a proper
JVM provided solution
+ * mentioned in
+ * <a href="https://bugs.openjdk.java.net/browse/JDK-4724038";>JDK-4724038:
Add unmap method to
+ * MappedByteBuffer</a>. The issue here is that even when closed, memory
mapped byte buffers
+ * hold a lock on the underlying file until GC is executing and this in
turns result in an error
+ * if the user tries to move or delete the file.
+ *
* @param buf the buffer to be unmapped
*/
public static void unmap(ByteBuffer buf)
