-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Possible memory leak? #1466
Comments
Hi John, It's possible that it's related to #1284. In that issue, we concentrated mostly on the spectacular virtual memory leak, but there was also an apparent but more modest increase in the resident memory used (that one seemed to stop growing after a few hundred megs). If you still have your instance running, you might look at the virtual memory being used. Another potential thing to try is to "stimulate" file watchers by quickly changing a file, within your workspace, and see if the memory seems to leak faster. e.g. run something like:
Where you change Without such stimulation, there could still be a slower leak, when some Theia extensions trigger file watcher. e.g. the git extension seems to do so once every few seconds. |
It does look like it's leaking virtual memory:
|
Another symptom of this leak is that it clears when the front-end is reloaded. If that happens too in your case, then this is probably a duplicate of #1284. I think it would be interesting for you to add to that issue, what you reported above, since I think we have not yet documented the leak in resident memory. We have insulated the problem to the file watcher library we use, called "nsfw", and reported the issue on their GH: Axosoft/nsfw#48 , but had no time yet to dig deeper or try to fix it ourselves. |
Yes, reloading the front end frees up both the virtual and resident memory
|
closing as duplicate of #1284 |
I pulled and ran the theiaide/theia image from Docker Hub, and left it overnight with a client connected. Using
docker stats
to monitor the memory usage, when it started it was using 120MB, but after 18 hours of being up but doing nothing, memory was at 215MB.The text was updated successfully, but these errors were encountered: