-
Bug
-
Resolution: Fixed
-
P3
-
hs14
-
b05
-
generic
-
solaris
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2204519 | 7 | Tony Printezis | P3 | Closed | Fixed | b124 |
JDK-2205836 | 6u25 | Tony Printezis | P3 | Closed | Fixed | b01 |
The following probes are not fired in case G1 is used:
hotspot:::gc-begin
hotspot:::gc-end
hotspot:::mem-pool-gc-begin
hotspot:::mem-pool-gc-end
The probes are not fired for both client and server compiler, on all solaris platforms.
hotspot:::gc-begin
hotspot:::gc-end
hotspot:::mem-pool-gc-begin
hotspot:::mem-pool-gc-end
The probes are not fired for both client and server compiler, on all solaris platforms.
- backported by
-
JDK-2204519 G1: hotspot:::gc and hotspot:::mem-pool-gc probes are not fired
- Closed
-
JDK-2205836 G1: hotspot:::gc and hotspot:::mem-pool-gc probes are not fired
- Closed
- relates to
-
JDK-7009379 G1: Dtrace probes in G1 are not correct
- Resolved
-
JDK-6458402 3 jvmti tests fail with CMS and +ExplicitGCInvokesConcurrent
- Closed
-
JDK-6941275 G1: The MemoryPools are incorrectly supported for G1
- Closed