| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2206385 | 7 | Tony Printezis | P2 | Closed | Fixed | b129 |
| JDK-2206994 | 6u25 | Tony Printezis | P2 | Closed | Fixed | b03 |
| JDK-2206241 | hs20 | Tony Printezis | P2 | Closed | Fixed | b10 |
Since the push of 6977804: G1: remove the zero-filling thread we are seeing intermittent JPRT failures with GCBasher / G1, mainly with product builds. The failure usually complains about a double free, like this one:
*** glibc detected ***
> >>>>> /tmp/jprt/P2/T/111410.et151817/testproduct/linux_x64_2.4-product/bin/java:
> >>>>>
> >>>>> double free or corruption (!prev): 0x00007f59c8524ce0 ***
I also saw (once) a failure in fastdebug complaining about an apparent inconsistency in the RSets:
# Internal Error (/tmp/jprt/P3/B/164311.ap31282/source/src/share/vm/gc_implementation/g1/sparsePRT.cpp:172),
pid=20790, tid=1083717968
# guarantee(_entries != NULL) failed: INV
*** glibc detected ***
> >>>>> /tmp/jprt/P2/T/111410.et151817/testproduct/linux_x64_2.4-product/bin/java:
> >>>>>
> >>>>> double free or corruption (!prev): 0x00007f59c8524ce0 ***
I also saw (once) a failure in fastdebug complaining about an apparent inconsistency in the RSets:
# Internal Error (/tmp/jprt/P3/B/164311.ap31282/source/src/share/vm/gc_implementation/g1/sparsePRT.cpp:172),
pid=20790, tid=1083717968
# guarantee(_entries != NULL) failed: INV
- backported by
-
JDK-2206241 G1: RSet-related failures
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-6977804 G1: remove the zero-filling thread
-
- Closed
-