Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 24
Affects Version/s: 24
Component/s: core-libs
Labels:
- release-note=yes

Subcomponent:
java.nio
Resolved In Build:
b26
CPU:

generic
OS:

generic

The failures reported in ~~JDK-8342849~~ and ~~JDK-8340728~~ are at bottom due to temporary direct buffers being allocated before the respective tests are actually run. This unpredictability makes the fix for ~~JDK-8340728~~ ugly and that for ~~JDK-8342849~~ difficult if not impossible. Not counting the memory used by internal temporary direct buffers toward the direct buffer memory upper limit would remove this uncertainty.

csr for

JDK-8344997 (bf) Temporary direct buffers should not count against the upper limit on direct buffer memory

Closed

relates to

JDK-8346576 Remove vmTestbase/gc/memory/Nio/Nio.java from test/hotspot/jtreg/ProblemList.txt

Resolved

JDK-8345421 (bf) Create specific test for temporary direct buffers and the buffer size limit

Resolved

JDK-8345181 (ch) Windows asynchronous channels may return temporary direct buffers to the buffer cache twice (win)

Closed

JDK-8340728 Test vmTestbase/gc/memory/Nio/Nio.java is failing to allocate all direct buffer memory

Closed

JDK-8342849 (bf) java/nio/Buffer/LimitDirectMemory.java fails with OutOfMemoryError

Closed

JDK-8339782 java/nio/channels/FileChannel/TempDirectBuffersReclamation.java failed AssertionError: Direct BufferPool not same before thread activity and after thread exit.

Closed

links to

Commit(master) openjdk/jdk/0312694c

Review(master) openjdk/jdk/22339

(2 relates to, 2 links to)

There are no Sub-Tasks for this issue.

Assignee:: Brian Burkhalter

Reporter:: Brian Burkhalter

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024-11-22 10:53

Updated:: 2024-12-18 08:50

Resolved:: 2024-11-27 08:15

Details

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates