-
Notifications
You must be signed in to change notification settings - Fork 29
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 somewhere, bot creating 40 thousand string objects #51
Comments
Hm. Very strange. I don't recognize any of those strings but they look like they relate to libraries that Node.js is including. What method are you using to generate and view the heapdump? Also, is there a way to check how the memory usage increases over time? |
@dsamarin I have just pulled the latest version of this bot down, so i will show an example of me using heapdump again. I've basically made a user command that dumps it, so i can make a new dump whenever, i've left the bot running for a day, then made a second dump, and compared the two. The new bot is still memory leaking to a high degree. unfortunately that heapdump isn't helping me locate where the problem is happening :/ |
@dsamarin
see this branch...
Although this doesn't seem much, after leaving the bot running for a day or 2, its memory usage goes up to 20% of the whole system, and ends up being killed by the kernal |
ended up using node-inspector instead, looks like some of those strings are coming from the node core itself |
The heapdump you included doesn't seem all that terrible (most of them are code / function names). Might be useful if you could take diff's somehow. |
@yorickvP I will try and get you some diffs
7.6 is quite high, considering i have a bot in python which is more huge (https://github.com/ProgVal/Limnoria) writing to the DB, generating logs etc and only using 2.8
|
I've been inspecting with heapdump (i can attach the file if people need)
http://imgur.com/a/iCuqA
The text was updated successfully, but these errors were encountered: