Kris Zyp
Kris Zyp
Sorry, I realize I have been slow with this, as I felt like this change was a bit more than a patch release since it involves some changes to the...
No, this isn't a known issue, and there wasn't a lot that changed between 2.2.0 and 2.2.1 (https://github.com/DoctorEvidence/lmdb-js/compare/v2.2.0...v2.2.1), the main things were some changes to how compression is instantiated (you...
While I haven't found any regressions, I did actually add some optimizations for clearing memory better for large number of writes that occur in a single event turn/txn (as in...
I tried this out locally and getting the same error. And I have tried this with a stripped-down barebones native .node module, still get this error or `Module did not...
That's good to hear that you had some success. I think I have heard of people using [nexe](https://github.com/nexe/nexe) too (I haven't tried it). I'd still be interested in figuring out...
As it turns out, the issue was due the `win_delay_load_hook: false` flag. This is a rather cryptic bit of node-gyp configuration that I had thought was helpful for electron. I...
Seems like electron loads fine with this flag removed.
I don't think that I can tell what is occurring from this information alone, but I have added some additional details for the error messages when a MDB_PROBLEM occurs to...
Have you ever seen this error again (with the more detailed error message)? Still would be interested in knowing what caused this.
That issue (#156) has been fixed though, so you can use latest now, right?