The PrintInlining output always reports a call site candidate for incremental inlining as "inline (hot)" whether the call site is actually inlined or not which results in duplicate lines most of the time (one "inline (hot)" and one "live nodes > LiveNodeCountInliningCutoff").
- relates to
-
JDK-8235998 [C2] Memory leaks during tracing after "8224193: stringStream should not use Resource Area".
-
- Resolved
-