Skip to content
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

Memory leaking #236

Closed
emcodemall opened this issue Mar 27, 2018 · 3 comments
Closed

Memory leaking #236

emcodemall opened this issue Mar 27, 2018 · 3 comments
Assignees
Labels

Comments

@emcodemall
Copy link

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?

@pablojan
Copy link
Contributor

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.

@pablojan pablojan self-assigned this Mar 28, 2018
@emcodemall
Copy link
Author

emcodemall commented Mar 28, 2018

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):
swell

I'll try to start the java vm with remote jmx enabled in order to do memory dumps in the next days.

@emcodemall
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants