-
Bug
-
Resolution: Fixed
-
P3
-
16
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8253347 | 15.0.2 | Manoj Gupta | P3 | Closed | Fixed | b01 |
| JDK-8256342 | 13.0.6 | Yuri Nesterenko | P3 | Resolved | Fixed | b01 |
| JDK-8253558 | 11.0.10-oracle | Harold Seigel | P3 | Resolved | Fixed | b01 |
| JDK-8253480 | 11.0.10 | Jaroslav Bachorík | P3 | Resolved | Fixed | b01 |
| JDK-8253596 | openjdk8u282 | Jaroslav Bachorík | P3 | Resolved | Fixed | b01 |
After JDK-8250928 JfrStackTrace::record_safe is using new, improved hash code calculation.
However, JfrStackTrace::record_thread was not updated to this calculation and we ended up with two ways a stack trace hash code will be calculated.
This situation does not sound right and JfrStackTrace::record_thread should be updated to use the new hash code calculation as well.
However, JfrStackTrace::record_thread was not updated to this calculation and we ended up with two ways a stack trace hash code will be calculated.
This situation does not sound right and JfrStackTrace::record_thread should be updated to use the new hash code calculation as well.
- backported by
-
JDK-8253480 Hash code calculation of JfrStackTrace is inconsistent
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-8250928 JFR: Improve hash algorithm for stack traces
-
- Resolved
-
(1 relates to, 2 links to)