AlexanderPrendota
commented
3 years ago Hey, did u try to increase the memory limit?
Open aaronsarkissian opened 3 years ago
AlexanderPrendota
commented
3 years ago Hey, did u try to increase the memory limit?
aaronsarkissian
commented
3 years ago Hey, did u try to increase the memory limit?
At first, it was about 1500MB, then I increased it to 2500MB, which didn't really help much. But I can try 4GB too.
Meanwhile, I'm suspecting that there is a code which causes this. Possible issue?
wayfarer-rus
commented
3 years ago if it possible, could you provide code snippet that causes the issue?
Or maybe it just happens for any reason, just after some time passes?
aaronsarkissian
commented
3 years ago if it possible, could you provide code snippet that causes the issue?
Or maybe it just happens for any reason, just after some time passes?
Based on my last dead docker container stats, I can say that it worked and compiled, 3114 codes successfully, and then the first issue began with the following error:
Script execution time in millis: 1506
Script execution time in millis: 1558
Script execution time in millis: 1503
Script execution time in millis: 1574
Script execution time in millis: 379
2021-06-13 10:01:21.376 INFO 1 --- [nio-8080-exec-3] o.s.core.annotation.MergedAnnotation : Failed to introspect annotations on public com.compiler.server.model.ExecutionResult com.compiler.server.controllers.CompilerRestController.testKotlinProjectEndpoint(com.compiler.server.model.Project): java.lang.OutOfMemoryError: Java heap space
2021-06-13 10:01:21.400 INFO 1 --- [nio-8080-exec-1] o.s.core.annotation.MergedAnnotation : Failed to introspect annotations on public com.compiler.server.model.ExecutionResult com.compiler.server.controllers.CompilerRestController.testKotlinProjectEndpoint(com.compiler.server.model.Project): java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-nio-8080-exec-2" Exception in thread "http-nio-8080-exec-8" java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2021-06-13 10:01:22.884 ERROR 1 --- [nio-8080-exec-9] o.a.coyote.http11.Http11NioProtocol : Failed to complete processing of a request
java.lang.OutOfMemoryError: Java heap space
2021-06-13 10:01:22.884 ERROR 1 --- [io-8080-exec-10] o.a.coyote.http11.Http11NioProtocol : Failed to complete processing of a request
java.lang.OutOfMemoryError: Java heap space
ERROR: Exception while analyzing expression at (2,15) in /File.kt
org.jetbrains.kotlin.utils.KotlinExceptionWithAttachments: Exception while analyzing expression at (2,15) in /File.kt
at org.jetbrains.kotlin.types.expreI encountered an issue with line endings so I have two regexes that replace:
(@"\r\n", "\n")
(@"\r", "\n")This fixed major crashes, but I don't have any known other cases yet.
So yes some time passes, usually a few days and this happens.
wayfarer-rus
commented
3 years ago Do you use Docker image from the project or custom?
If custom, which exact JVM do you use there?
I'm asking, because we haven't experienced any memory leaks yet. So, something must be different =)
AlexanderPrendota
commented
3 years ago I did not use the docker images for a while. I recommend to use AWS Lambda instead =)
aaronsarkissian
commented
3 years ago Do you use Docker image from the project or custom?
If custom, which exact JVM do you use there?
I'm asking, because we haven't experienced any memory leaks yet. So, something must be different =)
I forked the repo, added the optional userInput field, and built that docker image.
Do you think this userInput can cause a memory leak like this?
wayfarer-rus
commented
3 years ago Okay! Thanks for the info!
We'll build a stand and analyse the memory leak issue.
Stay tuned 😉
aaronsarkissian
commented
3 years ago Okay! Thanks for the info!
We'll build a stand and analyse the memory leak issue.
Stay tuned 😉
Thank you so much.
If it helps, I'm only using the ../api/compiler/run endpoint.
I run the dockerized version on my VM, which I use to compile codes, and after a while, it fails with the following error, and I should restart the docker container, so it works again.
Any suggestion? Can I config something which will prevent this from happening?
This is my docker-compose yaml part for the container: