-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 8u40, 8u65, 9
-
Component/s: core-libs
-
Environment:
-client -Xcomp
-
b70
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8135929 | emb-9 | Konstantin Shefov | P3 | Resolved | Fixed | team |
| JDK-8130981 | 8u65 | Konstantin Shefov | P3 | Resolved | Fixed | b05 |
| JDK-8129124 | 8u60 | Konstantin Shefov | P3 | Resolved | Fixed | b22 |
| JDK-8138289 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b05 |
| JDK-8130588 | emb-8u60 | Konstantin Shefov | P3 | Resolved | Fixed | b22 |
java/lang/invoke/TestCatchExceptionWithVarargs.java
java/lang/invoke/VarargsArrayTest.java
Issue could be reproduced with Client VM and Xcomp mode.
Code cache size for a Client VM is pretty small comparing to Server VM, about 32m, so it's pretty easy to run out of it, especially if a test generates many different methods.
I think that default code cache size for such tests should be increased.
- backported by
-
JDK-8129124 Several java/lang/invoke tests fail due to exhausted code cache
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-