-
Notifications
You must be signed in to change notification settings - Fork 21
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 leak? #22
Comments
Hello, I have spent some time tracking memory leaks. I found+fixed some. Not all, sorry. If anybody can find and fix the problem with a patch, it would be great. |
Thanks. Where can I find these fixes? are you referring to your collectw fork? I'm naturally a bit hesitant to try that, as it's over 2 years out of sync with this repo which has seemingly been updated a couple times since the fork |
The fixes are already in Collectm. Search for FYI, Collectw is not a fork. There used to be 2 Collectw projects. One has nothing to do with Collectm. The other one was renamed Collectm (no fork, just renamed). Again : this will not fix the memory leaks. If anybody can find and fix the problem with a patch, it would be great. |
When running CollectM for extended periods, memory consumed by the node.exe application increases continuously over time. In one case of a server that's been running for about 2 weeks, it is consuming nearly 2GB of RAM. What could possibly be causing this?
The text was updated successfully, but these errors were encountered: