Details
-
Sub-task
-
Resolution: Fixed
-
P4
-
None
-
b17
Description
[Thomas Schatzl]
Would it be possible to consider backing out the responsible change (JDK-8244778) if there is no quick fix available?
Almost all of my (local) specjbb2015 runs (simple compliant single-VM runs) crash with the change included, and I've heard from others that they get regular crashes in other perf testing (e.g. with JMH) too.
Would it be possible to consider backing out the responsible change (
Almost all of my (local) specjbb2015 runs (simple compliant single-VM runs) crash with the change included, and I've heard from others that they get regular crashes in other perf testing (e.g. with JMH) too.
Attachments
Issue Links
- duplicates
-
JDK-8253665 assert(!_g1h->is_humongous(desired_word_size)) failed: we should not be seeing humongous-size allocations in this path
- Closed
-
JDK-8253671 assert(!is_null(v)) failed: narrow klass value can never be zero
- Closed
- relates to
-
JDK-8253671 assert(!is_null(v)) failed: narrow klass value can never be zero
- Closed