| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2213964 | 8 | Daniel Daugherty | P3 | Resolved | Fixed | b03 |
| JDK-2213555 | 7u2 | Daniel Daugherty | P3 | Closed | Fixed | b04 |
| JDK-8017359 | 6u65 | Abhijit Saha | P3 | Closed | Fixed | b01 |
| JDK-8015137 | 6u60 | Abhijit Saha | P3 | Closed | Fixed | b01 |
| JDK-8011659 | 6u51 | Paul Nauman | P3 | Closed | Fixed | b03 |
| JDK-8011637 | 6u45 | Paul Nauman | P3 | Closed | Fixed | b31 |
| JDK-2209746 | 6u43 | Paul Nauman | P3 | Closed | Fixed | b31 |
A performance issue with the Hotspot implementation of FollowReferences causes
it to be 10x slower than JROckit.
There is an unnecessary reset of a "visited" flag on Java heap objects.
The flag is reset even when no objects are ever marked as visited.
See attached patch file and diffs for a suggested fix.
it to be 10x slower than JROckit.
There is an unnecessary reset of a "visited" flag on Java heap objects.
The flag is reset even when no objects are ever marked as visited.
See attached patch file and diffs for a suggested fix.
- backported by
-
JDK-2213964 JVMTI FollowReferences is slow
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-6951623 possible performance problems in FollowReferences() and GetObjectsWithTags()
-
- Closed
-
(2 backported by, 1 relates to)