- 
    Bug 
- 
    Resolution: Fixed
- 
     P2 P2
- 
    8u60, 9
- 
        b52
- 
        Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8084554 | emb-9 | Vladimir Ivanov | P2 | Resolved | Fixed | team | 
| JDK-8086903 | 8u65 | Vladimir Ivanov | P2 | Resolved | Fixed | b01 | 
| JDK-8071764 | 8u60 | Vladimir Ivanov | P2 | Closed | Fixed | b14 | 
| JDK-8138045 | emb-8u65 | Unassigned | P2 | Resolved | Fixed | b01 | 
| JDK-8080009 | emb-8u60 | Vladimir Ivanov | P2 | Resolved | Fixed | team | 
The cause is JIT compiler can't produce a single nmethod for the whole MethodHandle chain underneath, so the execution is spread around numerous nmethods (1 per each MethodHandle in the chain).
ILW = HLH = P2
I = H: performance regression (significant, in some situations)
L = L: only MH.invoke/invokeExact calls with non-constant receiver are affected
W = H: none
- backported by
- 
                    JDK-8080009 Customize LambdaForms which are invoked using MH.invoke/invokeExact -           
- Resolved
 
-         
- 
                    JDK-8084554 Customize LambdaForms which are invoked using MH.invoke/invokeExact -           
- Resolved
 
-         
- 
                    JDK-8086903 Customize LambdaForms which are invoked using MH.invoke/invokeExact -           
- Resolved
 
-         
- 
                    JDK-8138045 Customize LambdaForms which are invoked using MH.invoke/invokeExact -           
- Resolved
 
-         
- 
                    JDK-8071764 Customize LambdaForms which are invoked using MH.invoke/invokeExact -           
- Closed
 
-         
- relates to
- 
                    JDK-8063137 Never taken branches should be pruned when GWT LambdaForms are shared -           
- Closed
 
-         
- 
                    JDK-8046703 JEP 210: LambdaForm Reduction and Caching -           
- Closed
 
-