You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, i am currently testing swellrt on windows, compiled prod and using gradlew run to start as background service.
I see the memory consumption of java process growing every day (without using any function of the server). After around 3 days it gets slightly more than 1GB and therefore Memory problems using java default config.
Am i doing something wrong, is it different running the stuff as docker?
The text was updated successfully, but these errors were encountered:
Hi! thanks so much for reporting this. At a glance I guess it is a memory leak in the code. I am going to look into it asap. There is no difference in config whether you run it in docker or not. Please, let me know if you get further symptoms.
This is the error message i got at a client after a few days idle server and then about 1 hour testing (not very much editor text echange) from 2-3 concurrent clients (GC overhead limit exceeded):
I'll try to start the java vm with remote jmx enabled in order to do memory dumps in the next days.
Hey, i am currently testing swellrt on windows, compiled prod and using gradlew run to start as background service.
I see the memory consumption of java process growing every day (without using any function of the server). After around 3 days it gets slightly more than 1GB and therefore Memory problems using java default config.
Am i doing something wrong, is it different running the stuff as docker?
The text was updated successfully, but these errors were encountered: