Memory leak with MySQL Database

[spaceribs]

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?

[trichner]

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]

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).