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
Process killed when live-reload quarkus Java application #2360
Comments
Thanks for reporting this! This seems to happen because of "internal_proxy": {"idle_timeout": 10} The timeout is in seconds, and by default it is 5 seconds. Can you try increasing it and seeing if it happens again? |
Actually I increased the Also, the performance in VSCode is greatly impact, much slower, compare to using I haven't tried with manul saving (manual compilation) in VSCode but I doubt it will work, since there is less synchronization happening. |
Can you attach the same log as above reproduced with the new idle timeout please? |
Sure, this is the trace log And the configuration is "internal_proxy": {
"log_destination": "/tmp/internal_proxy.log",
"log_level": "mirrord=trace",
"idle_timeout": 1200
} |
I see it fails on accessing {
"feature": {
"fs": {
"mode": "read",
"local": ["/workspace.+"]
}
}
} |
I tried with the above configuration, Quarkus process did not get killed this time but the performance of VSCode is much slower or freeze for code completion, suggestion, compare to not using that configuration. Sometimes the VSCode debugger is even terminated while I write some code. Increasing the memory of Java language server helped with the slowing / freezing of VSCode (not entirely) but I don't need to do that if I use Do you think using the |
It could be that we're attached to the debugger as well, making it a bit slower. |
Bug Description
I used
mirrord
to start a quarkus Java application in dev mode for live reloading of the application in development. And I use VSCode in devcontainer for my local development workspace. After a while of implementing, my VSCode freezes and the Java process is killed, along with the agentCommand to start quarkus Java application
mirrord -f .mirrord/mirrord.json mvn quarkus:dev
Mirrord configuration
launch.json
for attaching the local debuggerThe trace log is large so I attached it below
internal_proxy.log
Steps to Reproduce
Backtrace
No response
Relevant Logs
No response
Your operating system and version
java GraalVM CE 21.0.2+13.1 (build 21.0.2+13-jvmci-23.1-b30)
Local process
java
Local process version
java 17 grralvm
Additional Info
However, if I start a new
bash
session usingmirrord
mirrord -f .mirrord/mirrord.json bash
Then run the quarkus Java application in dev mode
mvn quarkus:dev
Then the above issue never happens, the performance is better, VSCode does not freeze and the Java process is not killed
The text was updated successfully, but these errors were encountered: