10000 Memory leak with MySQL Database · Issue #91 · trichner/Metropolis · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Memory leak with MySQL Database #91

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
Open
spaceribs opened this issue Jun 16, 2014 · 2 comments
Open

Memory leak with MySQL Database #91

spaceribs opened this issue Jun 16, 2014 · 2 comments
Labels
bug

Comments

@spaceribs
Copy link
Collaborator

Everyone already knows about this issue, but I wanted to make sure it's in the issue tracker. I'm getting OOM kills using 6gb max memory for java (7gb for the box, any more and it crashes my system). I'm not sure if it's a matter of closing database objects after we're done using them, but it's a serious barrier at the moment and it needs to be fixed.

MySQL is showing the lions share spent in VisualVM, is there anything I can do to hunt this memory leak down myself?
@spaceribs spaceribs added the bug label Jun 16, 2014
@trichner
Copy link
Owner

are you on the newest version? I have no memory leak. But yes it uses up a
lot of ram.

2014-06-16 18:56 GMT+02:00 spaceribs notifications@github.com:

Everyone already knows about this issue, but I wanted to make sure it's in
the issue tracker. I'm getting OOM kills using 6gb max memory for java (7gb
for the box, any more and it crashes my system). I'm not sure if it's a
matter of closing database objects after we're done using them, but it's a
serious barrier at the moment and it needs to be fixed.

MySQL is showing the lions share spent in VisualVM, is there anything I
can do to hunt this memory leak down myself?

—
Reply to this email directly or view it on GitHub
#91.

@spaceribs
Copy link
Collaborator Author

Load up the vagrant box at some point and see for yourself, you can adjust up the memory requirement from the current 6gb in the Vagrantfile but right now it'll get killed at around 300 of 500 schematics loaded (not even built into the grid).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@spaceribs @trichner
0