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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃洜 update lodash,knex and bookshelf to latest versions #7402
馃洜 update lodash,knex and bookshelf to latest versions #7402
Conversation
Is that the same or different to the previous test? Can you maybe share a graph of both? If I am remembering correctly, this same test did not reproduce the memory leak last time, and so this is not a good test to base an conclusion on? I now have access to a trace account, so maybe we can setup a longer running test tomorrow ? |
Same. I don't have a graph.
I was able to reproduce the memory leak with this exact test suite. And now it's gone with the new knex bump.
If you want sure. My ghost server is running now an hour and memory is good. |
When I asked you if it was the same, I meant the results, not the test itself (you stated in your PR that the test was the same test). I'm asking how these results compare to the results you saw last time? I want to see side-by-side results so that I can understand the difference, if there is one. |
I can make graphs tomorrow 馃憤 with knex 0.10 (which we are using now), knex 0.11 (which had a memory leak) and knex 0.12. (which solved the memory leak) |
Either a graph or a table would be fab. |
I'll need to take a look to see what's happening here |
@kirrg001 is there a step-by-step I can follow to reproduce those graphs and get those results? |
Just in looking through the commit log I believe the issue likely has to do with the If it is indeed the source of issue I can go ahead and revert the portions that change asap, will try and take a look a little later. |
@tgriesser Thanks for getting involved. To reproduce the problem, you need to checkout this branch and setup a ghost blog with a bigger database (i had 20 posts in my database). Then you can trigger some curl commands from shell and watch the memory. Write me a PM in slack, if you need help. see also #7189 |
This is fixed in Bookshelf 0.10.2 馃帀 - Thanks @kirrg001 for the help in profiling / tracking this one down! |
3706448
to
a3cbbed
Compare
I can confirm: the memory leak is fixed in |
ready for review && merge |
@kirrg001 this needs rebasing please :) |
@ErisDS 馃憤 馃憤 didn't see, will do now |
refs TryGhost#7189 - we had a memory leak after upgrading to knex 0.11.x - knex has published a new version 0.12.x - the memory leak does not longer exists - knex has reverted their pool logic, see knex/knex#1665
a3cbbed
to
6c100a1
Compare
@ErisDS did |
I would like this same PR made to the |
@ErisDS sure will create |
refs #7189
0.10.2