-
Bug
-
Resolution: Fixed
-
P3
-
25, 26
-
b05
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8362047 | 25.0.1 | Erik Gahlin | P3 | Resolved | Fixed | b02 |
JDK-8361377 | 25 | Erik Gahlin | P3 | Resolved | Fixed | b31 |
To reduce regression when starting JDK 25, the PlatformTracer class used by the MethodTiming and MethodTrace events should only be used if a filter has been set. Most application starts will not use these events, so it makes sense to avoid using them unless needed.
- backported by
-
JDK-8361377 JFR: PlatformTracer class should be loaded lazily
-
- Resolved
-
-
JDK-8362047 JFR: PlatformTracer class should be loaded lazily
-
- Resolved
-
- links to
-
Commit(jdk25) openjdk/jdk/e3bd9c6e
-
Commit(master) openjdk/jdk/8ea544c3
-
Review(jdk25) openjdk/jdk/26040
-
Review(master) openjdk/jdk/25937
(1 links to)