I don't think that it is correct channel for this question, but probably to improve chance to fix it you need some reproducible sample or maybe debug logs
e
Eugen Martynov
05/27/2019, 2:35 PM
It doesn’t happen all the time
Eugen Martynov
05/27/2019, 2:37 PM
i can enable debug log and pack it as artifact in CI build but as for now I have limited space and bandwidth on CI system, so would like wait it there are other potions to trace this issue
t
tapchicoma
05/27/2019, 2:56 PM
as I recall - there were similar issues in the past (you can search on youtrack) that was marked as fixed. Possibly you need properly say what memory is available to JVM on CI (this is the case if you are using CircleCI)
s
Sergei Dubrov [JB]
05/27/2019, 4:40 PM
Hi Eugen. I have moved the issue to developers. But I am not sure if the stacktrace is enough for understanding the root cause. Can you attach the log mentioned in stacktrace to the issue?
e
Eugen Martynov
05/27/2019, 8:32 PM
Hi Sergey, I will update more details about issue, I will also search for the past issue