None.
Issue |
Description |
JDK-8218472 |
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported
for use by the Swing GTK Look And Feel in this release.
Affected applications on such configurations should specify the system property
-Djdk.gtk.version=2.2 to request GTK2+ based rendering instead.
|
JDK-8218469 |
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported for use by the Swing GTK Look And Feel in this release.
|
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported
for use by the Swing GTK Look And Feel in this release.
Affected applications on such configurations should specify the system property
-Djdk.gtk.version=2.2 to request GTK2+ based rendering instead.
|
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported
for use by the Swing GTK Look And Feel in this release.
Affected applications on such configurations should specify the system property
-Djdk.gtk.version=2.2 to request GTK2+ based rendering instead.
|
JDK-8218479 |
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported
for use by the Swing GTK Look And Feel in this release.
Affected applications on such configurations should specify the system property
-Djdk.gtk.version=2.2 to request GTK2+ based rendering instead.
|
JDK-8218470 |
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported
for use by the Swing GTK Look And Feel in this release.
Affected applications on such configurations should specify the system property
-Djdk.gtk.version=2.2 to request GTK2+ based rendering instead.
|
JDK-8218473 |
GTK+ 3.20 and Later Unsupported by Swing
Due to incompatible changes in the GTK+ 3 library versions 3.20 and later,
the Swing GTK Look and Feel does not render some UI components when using this library.
Therefore Linux installations with versions of GTK+ 3.20 and above are not supported
for use by the Swing GTK Look And Feel in this release.
Affected applications on such configurations should specify the system property
-Djdk.gtk.version=2.2 to request GTK2+ based rendering instead.
|
Priority |
Bug |
Summary |
P2 |
JDK-8217794 |
Missing termination check results violation of termination invariant |
P3 |
JDK-8220344 |
Build failures when using --with-jvm-features=-g1gc,-jfr |
P3 |
JDK-8218880 |
G1 crashes when issuing a periodic GC while the GCLocker is held |
P3 |
JDK-8220161 |
Shenandoah does not need to initialize PLABs for safepoint workers |
P3 |
JDK-8220153 |
Shenandoah does not work with TransparentHugePages properly |
P3 |
JDK-8219524 |
Shenandoah misreports "committed" size in MemoryMXBean |
P3 |
JDK-8220162 |
Shenandoah should not commit HugeTLBFS memory |
P4 |
JDK-8217342 |
Build failed with excluding JFR |
P4 |
JDK-8217319 |
Cleanup Shenandoah includes |
P4 |
JDK-8217014 |
Epsilon should not ignore Metadata GC causes |
P4 |
JDK-8219976 |
GarbageCollectionNotificationInfo always says "No GC" when running Shenandoah |
P4 |
JDK-8220812 |
gc/shenandoah/options/TestLoopMiningArguments.java fails if default GC is serial/parallel/cms |
P4 |
JDK-8220228 |
Improve Shenandoah pacing histogram message |
P4 |
JDK-8217432 |
MetaspaceGC::_capacity_until_GC exceeds MaxMetaspaceSize |
P4 |
JDK-8217400 |
Optimized build is broken by Shenandoah changes |
P4 |
JDK-8220350 |
Refactor ShenandoahHeap::initialize |
P4 |
JDK-8218192 |
Remove copy constructor for MemRegion |
P4 |
JDK-8215299 |
Remove G1CMTask::should_exit_termination()'s undesirable side-effect |
P4 |
JDK-8217343 |
Shenandoah control thread should be able to run at critical priority |
P4 |
JDK-8215549 |
Shenandoah deduplication cleans up table/queue twice |
P4 |
JDK-8219857 |
Shenandoah GC may initialize thread's gclab twice |
P4 |
JDK-8220546 |
Shenandoah Reports timing details for weak root processing |
P4 |
JDK-8221278 |
Shenandoah should not enqueue string dedup candidates during root scan |
P4 |
JDK-8220444 |
Shenandoah should use parallel version of WeakProcessor in root processor for weak roots |
P4 |
JDK-8216973 |
Shenandoah: Kick up cleanup phases in the right places |
P4 |
JDK-8203232 |
Shenandoah: Resolve oops in SATB filter |
P4 |
JDK-8217016 |
Shenandoah: Streamline generation of CAS barriers |
P4 |
JDK-8220780 |
ShenandoahBS::AccessBarrier::oop_store_in_heap ignores AS_NO_KEEPALIVE |
P4 |
JDK-8217213 |
shenandoahTaskQueue.hpp includes .inline.hpp file |
P4 |
JDK-8215047 |
Task terminators do not complete termination in consistent state |
P4 |
JDK-8220294 |
ZGC fails to build on GCC 4.4.7: Type parameter issue |
Priority |
Bug |
Summary |
P2 |
JDK-8217765 |
Internal Error (javaCalls.cpp:61) guarantee(thread->can_call_java()) failed |
P2 |
JDK-8219974 |
REDO JDK-8219492: Restore static callsite resolution for the current class |
P3 |
JDK-8216559 |
[JFR] Native libraries not correctly parsed from /proc/self/maps |
P3 |
JDK-8219712 |
code_size2 (defined in stub_routines_x86.hpp) is too small on new Skylake CPUs |
P3 |
JDK-8210457 |
JVM crash in ResolvedMethodTable::add_method(Handle) |
P3 |
JDK-8200109 |
NMT: diff_malloc_site assert(early->flags() == current->flags(), "Must be the same memory type") |
P3 |
JDK-8216049 |
stringTable::intern creates redundant String when looking up existing one |
P4 |
JDK-8215398 |
-Xlog option usage => Invalid decorator '\temp\app_cds.log'. |
P4 |
JDK-8219698 |
aarch64: SIGILL triggered when specifying unsupported hardware features |
P4 |
JDK-8217994 |
os::print_hex_dump should be more resilient against unreadable memory |
P4 |
JDK-8217315 |
Proper units should print more significant digits |
P4 |
JDK-8216302 |
StackTraceElement::fill_in can use cached Class.name |
P4 |
JDK-8216308 |
StackTraceElement::fill_in can use injected Class source-file |
P4 |
JDK-8219584 |
Try to dump error file by thread which causes safepoint timeout |
P4 |
JDK-8217378 |
UseCriticalCMSThreadPriority is broken |
P4 |
JDK-8220283 |
ZGC fails to build on GCC 4.4.7: ATTRIBUTE_ALIGNED compatibility issue |