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.

Sign up for GitHub

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

Jump to bottom

OOM on k8s burndown with merges #142

Closed

vmarkovtsev opened this issue Dec 14, 2018 · 1 comment

Collaborator

vmarkovtsev commented Dec 14, 2018

Hercules consumes more than 128GB memory for burndown analysis on k8s with merges inspected. There can be a memory leak.

Collaborator Author

vmarkovtsev commented Jan 18, 2019

This is fixed in v6

vmarkovtsev closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment