-
Bug
-
Resolution: Fixed
-
P4
-
hs17
-
b06
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2187071 | 7 | Y. Ramakrishna | P4 | Closed | Fixed | b79 |
JDK-2189873 | 6u21 | Y. Ramakrishna | P4 | Resolved | Fixed | b01 |
Having collected the debugging data related to 6898948 from two nights of
testing, we want to turn off the assert following the data
dumping by protecting with a debug flag defaulting to false.
This will allow the debug JVM to, by default, correct the
problem and continue operation, just as in product mode,
rather than failing upon encountering the problem.
testing, we want to turn off the assert following the data
dumping by protecting with a debug flag defaulting to false.
This will allow the debug JVM to, by default, correct the
problem and continue operation, just as in product mode,
rather than failing upon encountering the problem.
- backported by
-
JDK-2189873 G1: protect debugging code related to 6898948 with a debug flag
- Resolved
-
JDK-2187071 G1: protect debugging code related to 6898948 with a debug flag
- Closed
- relates to
-
JDK-6886024 G1: assert(recent_avg_pause_time_ratio() < 1.00,"All GC?")
- Resolved
-
JDK-6902692 G1: g1CollectorPolicy.cpp:1533, assert(false,"Debugging data for CR 6898948 has been dumped above")
- Closed
-
JDK-6898948 G1: forensic instrumentation for out-of-bounds recent_avg_pause_time_ratio()
- Resolved