-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.VirtualMachineError: Out of space in CodeCache for method handle intrinsic #582
Comments
It is known issue reported here: there is workaround |
Artur-
added a commit
to vaadin/intellij-plugin
that referenced
this issue
Sep 4, 2024
MarcinVaadin
added a commit
to vaadin/intellij-plugin
that referenced
this issue
Sep 4, 2024
* feat: Debug using Hotswap Agent * Fallback to bundled JBR if Java version is compatible Bundle and copy hotswap agent * Add --add-opens which may or may not be needed * Detect project Java target version * Use HotswapAgent from ~/.vaadin/intellij * Extract helpers * fix typo * Show error if no suitable JBR is found * icon * Fix Out of space in CodeCache for method handle intrinsic See HotswapProjects/HotswapAgent#582 * Use hotswap agent 2.0.0 * Properly add opens arguments * const * More opens * use VaadinIcons * use proper classloader --------- Co-authored-by: marcin <[email protected]>
I get this even with With the default, I run out of CodeCache pretty quickly, but even after doing Default:
After increasing:
|
Problem should be is fixed in last JBR 21 version and it works without any additional options. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reporting this on behalf of other people as I have not experienced it myself nor do I know if it is expected or some kind of problem.
Anyway, it seems like even after a few hotswaps (around 5) you might run into this
java.lang.VirtualMachineError: Out of space in CodeCache for method handle intrinsic
orIs this something common that others run into? I found some old JDK bugs that were resolved related to this
The text was updated successfully, but these errors were encountered: