Hello Marko,
core-libs-dev@openjdk.org is better suited for this kind of question.
You can submit a bug using bugreport.java.com with all the details you have.
Regards,
Alexey
On 2024-09-04 13:50, Marko Bakšić wrote:
Hey there!
Sorry for coming here with a technical question, but I would
a
just opened
this issue https://bugs.openjdk.org/browse/JDK-8309726, and it was
*the OpenJDK infrastructure* which in turn posted to the "wrong" list.
I am not aware who is in charge to fix this, but *I* cannot change
this behvior. Maybe the one in charge is reading this and can fix it?
Hi Markus,
You posted it to the wrong list, it belongs on core-libs-dev.
--
Regards,
Alexey
On 10/06/2023 12:35, Markus Karg wrote:
By analyzing several existing applications I noticed that many of them
need to read a String from an input source (be it an input stream or a
reader), and ther
Hi Robin,
This belongs in core-libs.
On 24/05/2023 16:50, Robin Gong wrote:
Hi,
Recently, I found this constructor in PriorityBlockingQueue:
public PriorityBlockingQueue(int initialCapacity,
Comparator comparator) {
if (initialCapacity <
On 06/03/2023 13:51, Albert Yang wrote:
Upon a cursory inspection of ForceGC.java, it seems that the fundamental logic
involves waiting for a certain duration and relying on chance. However, I am of
the opinion that utilizing the WhiteBox API can provide greater determinism and
potentially str
ocating lots of memory.
s'marks
On 3/3/23 10:02 AM, Aleksei Ivanov wrote:
Hello,
In clientlibs, there's occasionally a need to verify an object isn't
leaked. For this purpose, WeakReference or PhantomReference is used.
Then, we need to make the reference object be cleared, s
Hello,
In clientlibs, there's occasionally a need to verify an object isn't
leaked. For this purpose, WeakReference or PhantomReference is used.
Then, we need to make the reference object be cleared, so a GC cycle
need to be triggered. The common approach is generating
OutOfMemoryError, catc
