-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b28
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8012403 | 8 | Krystal Mo | P4 | Closed | Fixed | b86 |
JDK-8018322 | 7u45 | Krystal Mo | P4 | Closed | Fixed | b01 |
JDK-8013984 | 7u40 | Krystal Mo | P4 | Closed | Fixed | b24 |
JDK-8013106 | hs24 | Krystal Mo | P4 | Closed | Fixed | b42 |
There are some TraceMethodHandles logic that uses Symbol::as_C_string(), but miss putting a ResourceMark in the appropriate scope, triggering assertions in debug builds when using -XX:+TraceMethodHandles.
- backported by
-
JDK-8012403 Missing ResourceMarks in TraceMethodHandles
-
- Closed
-
-
JDK-8013106 Missing ResourceMarks in TraceMethodHandles
-
- Closed
-
-
JDK-8013984 Missing ResourceMarks in TraceMethodHandles
-
- Closed
-
-
JDK-8018322 Missing ResourceMarks in TraceMethodHandles
-
- Closed
-
- relates to
-
JDK-7023639 JSR 292 method handle invocation needs a fast path for compiled code
-
- Closed
-