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 leak #2

Open
timg83 opened this issue Sep 7, 2017 · 2 comments
Open

Memory leak #2

timg83 opened this issue Sep 7, 2017 · 2 comments

Comments

@timg83
Copy link

timg83 commented Sep 7, 2017

We have Cradiator running to have insight of our builds. Currently we monitor 8 builds using this tool. After a while (let's say a few weeks) the amount of memory the tool uses is almost 3GB! Our monitoring system becomes unresponsive due to insufficient memory and we have to reboot the system.

@PandaWood
Copy link
Owner

Thanks, yes I've noticed this.
In fact I neglected to raise the issue myself when moving back to to GitHub from CodePlex.

I made a change a while to something that I thought might be contributing to a leak but I will need to do some more leak debugging -
6b05a68

@timg83
Copy link
Author

timg83 commented Sep 11, 2017

It seems like we had an older version of the sources running. I've pulled the latest version and compiled it. Let's see what happens after a while.

Keep you posted :)

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

No branches or pull requests

2 participants