On Wed, 19 Feb 2025 09:14:03 GMT, Per Minborg wrote:
> This PR proposes to clarify the documentation for two of the
> `MemorySegment::reinterpret` overloads.
This pull request has now been integrated.
Changeset: f755fadc
Author:Per Minborg
URL:
https://git.openjdk.org/jdk/commit/f7
On Mon, 24 Feb 2025 06:10:39 GMT, Kim Barrett wrote:
> And here is a bug and recently opened PR that would benefit from having
> Cleaner.waitForCleaning.
If you are suggesting exposing this as a public API then I don't think we
should do this, I actually think it's time to consider deprecatin
On Mon, 24 Feb 2025 05:50:40 GMT, Jaikiran Pai wrote:
> Can I please get a review of this test-only change which proposes to address
> an intermittent failure in the
> `test/jdk/java/util/zip/ZipFile/TestCleaner.java` test?
>
> This test does operations on Inflater/Deflater/ZipFile and closes
On Tue, 18 Feb 2025 14:33:16 GMT, Aleksey Shipilev wrote:
>> DirectByteBuffers are still using old `jdk.internal.ref.Cleaner`
>> implementation. That implementation carries a doubly-linked list, and so
>> makes DBB suffer from the same issue fixed for generic
>> `java.lang.ref.Cleaner` users w
Can I please get a review of this test-only change which proposes to address an
intermittent failure in the `test/jdk/java/util/zip/ZipFile/TestCleaner.java`
test?
This test does operations on Inflater/Deflater/ZipFile and closes those
instances and then waits for GC to kick in. After wait for
On Sun, 23 Feb 2025 11:32:41 GMT, Robert Stupp wrote:
> Concurent calls to `ClassLoader.definePackage()` can yield
> `IllegalArgumentException`s if the package is already defined. Some built-in
> class loaders, like `URLClassLoader`, already handle this case, but custom
> class loaders (would)
On Sat, 22 Feb 2025 14:30:11 GMT, Doug Lea wrote:
>> (Copied from https://bugs.openjdk.org/browse/JDK-8319447)
>>
>> The problems addressed by this CR/PR are that ScheduledThreadPoolExecutor is
>> both ill-suited for many (if not most) of its applications, and is a
>> performance bottleneck (a
> (Copied from https://bugs.openjdk.org/browse/JDK-8319447)
>
> The problems addressed by this CR/PR are that ScheduledThreadPoolExecutor is
> both ill-suited for many (if not most) of its applications, and is a
> performance bottleneck (as seen especially in Loom and CompletableFuture
> usages
On Sun, 23 Feb 2025 11:32:41 GMT, Robert Stupp wrote:
> Concurent calls to `ClassLoader.definePackage()` can yield
> `IllegalArgumentException`s if the package is already defined. Some built-in
> class loaders, like `URLClassLoader`, already handle this case, but custom
> class loaders (would)
Concurent calls to `ClassLoader.definePackage()` can yield
`IllegalArgumentException`s if the package is already defined. Some built-in
class loaders, like `URLClassLoader`, already handle this case, but custom
class loaders (would) have to handle this case.
This change updates the logic of `CL
On Tue, 18 Feb 2025 14:33:16 GMT, Aleksey Shipilev wrote:
>> DirectByteBuffers are still using old `jdk.internal.ref.Cleaner`
>> implementation. That implementation carries a doubly-linked list, and so
>> makes DBB suffer from the same issue fixed for generic
>> `java.lang.ref.Cleaner` users w
11 matches
Mail list logo
