Kris Zyp

If it helps at all, you can see this PR (and the node-gyp-build PR) in use with my https://www.npmjs.com/package/msgpackr-extract package, and platform packages at https://www.npmjs.com/org/msgpackr-extract .

I think this is the same as #289. @repeatedly and @frsyuki I know you are both probably very busy, but it would be really great to be able to get...

@frsyuki any chance you could take a look at this? I think MessagePack could benefit from having an updated list of implementations. Thanks!

I have tried running this script on Windows and OSX and haven't seen any type of unusual memory growth. How much memory growth are you seeing? Do you know what...

Do you know how to determine how much of that is shared memory (I don't know how to do that for sure in Ubuntu)? Shared memory reporting can be rather...

Does this problem exist in [email protected] or 0.9.2? Just wondering if it is possible that there is a bug in the code that tries to check if any other threads...

I could try looking at an ubuntu instance. I did try to see what memory usage looks like if I intentionally do not close any of the envs in your...

Yes, it is the case, and I've debugged/stepped through the code to verify that `munmap` is called when `env.close()` is called. And that's why I still suspect this has to...

I don't have any exact answer or solution, but here are some things I noticed: Paradoxically, the ballooning memory usage does not occur if you do _not_ close the environments....

Yeah, WSL1 has devastating and unpredictable bugs that can't be worked around. I was just running LMDB on WSL 2 this morning, and it works great.