-
Notifications
You must be signed in to change notification settings - Fork 6
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
Out of memory - possible memory leak #60
Comments
Do you have a clue what the date or commit is when this issue started happening? |
It was definitely working at the beginning of 2015. I think it started happening in the middle of January. It can possibly be related to when I switched from Windows to Linux. I noticed yesterday that the whole machine is going low on memory when this issue occurs. |
Does the amount of RAM used by this application increase steadily over time? |
Do you also have an example of a stack trace that the OOME left behind? While the cause is not necessarily in that specific method, it could still give some hints. |
I'll have to investigate about the RAM. I am not sure about that. There is no stack trace, unfortunately. |
This might have been fixed. The bot has survived for more than one day so far. Leaving issue open for a little longer in case it is not fixed. |
This is not fixed. It is confirmed to not be because of the comment scanning though. |
Duga has been up and running now for ten days without the need to restart her. http://chat.stackexchange.com/transcript/20298?m=21702930#21702930 |
Recently the Tomcat server is running out of memory. I believe this started to happen quite recently, possibly with either the Github API requests or the StackExchange API requests, or with the refactoring of the daily updates. Either way, try to locate this bug.
The text was updated successfully, but these errors were encountered: