Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 16
Affects Version/s: 16
Component/s: hotspot
Labels:
- gc-g1

Subcomponent:
gc
Resolved In Build:
b05

There are currently a lot of failures in tier7/8 that seem to be caused indirectly by ~~JDK-8244603~~. So while it does not seem to be the actual cause for the failures but most likely a latent bug uncovered by it, it generates a lot of noise.

In ~~JDK-8248438~~ [~dcubed] found out that all these failures started with ~~JDK-8244603~~.

duplicates

JDK-8248382 gc/g1/TestGCLogMessages.java fails - missing "Evacuation failure" message

Closed

JDK-8248438 SIGSEGV in ObjectMonitor::enter

Closed

JDK-8248442 Kitchensink24HStress.java SIGSEGV in G1ParScanThreadState::copy_to_survivor_space due to bad Handle

Closed

JDK-8248447 SIGSEGV in G1ScanHRForRegionClosure::scan_heap_roots

Closed

JDK-8248648 Dacapo24H.java failed "illegal bytecode sequence - method not verified"

Closed

JDK-8248649 Kitchensink24HStress.java SIGSEGV in G1CodeRootSet::nmethods_do

Closed

relates to

JDK-8244603 G1 incorrectly limiting young gen size when using the reserve can result in repeated full gcs

Resolved

JDK-8249192 MonitorInfo stores raw oops across safepoints

Closed

(1 duplicates, 2 relates to)

Assignee:: Thomas Schatzl
Reporter:: Thomas Schatzl
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: 2020-07-01 09:06
Updated:: 2024-11-13 10:00
Resolved:: 2020-07-02 00:46

Details

Description

Attachments

Issue Links

Activity

People

Dates