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
cannot install on node 10 #26
Comments
Hey @alvis. Thanks for pointing out! Yeah, let‘s use the fork‘s fork. Seems like the easiest solution :) Would you mind opening a PR? |
happy to do so |
okay. seems like it's not as straightforward as I thought. It's almost okay, but I got this test error if I swap
The indicates that the following code does not throw. leakage/test/integration.test.js Lines 11 to 18 in 5ee8c95
I'm not an expert in this area, but it seems like to me that the problem is due to the change in V8's GC. i.e. the gc calls in the following lines may not work as intended Lines 39 to 51 in 5ee8c95
any thought? |
No idea yet 😕 Gotta read up on the V8 garbage collector changes. Maybe it has become harder to trigger a full GC 🤔 |
It turns out that a simple replacement is just fine. What's not fine is the pressure of the test. The default 30 iterations on a small object This issue can be closed once #27 is merged. |
Closed by #27. Published as Thought about making it v1.0, but let's give it a little bit of time to be battle-tested first. |
memwatch-next is no longer supported and doesn't work under Node 10.16.0 (see [this issue](andywer/leakage#26)). Luckily it's not actually used for anything except a commented-out block of code. So removing the dependency doesn't break anything at all.
memwatch-next, an upstream dependence, doesn't support v8 6.6 and therefore preventing leakage to be installed on node 10. See marcominetti/node-memwatch#39
Should we swap memwatch-next with node-memwatch to solve the problem?
The text was updated successfully, but these errors were encountered: