https://bugs.openldap.org/show_bug.cgi?id=10552
--- Comment #4 from Howard Chu hyc@openldap.org --- (In reply to donxenapo from comment #2)
We have no way of knowing what triggers it (maybe you can advice where to look?), we just see that this happens on a significant percent of our users. It seems to happen immediately after they have created the database: it either gets corrupted almost immediately after just a couple Put requests, or it never gets corrupted.
If it does get corrupted, purging and recreating it often fixes the issue.
We presume that the issue might have something to do with the fact that we're not using the exact 1.0.0 version, instead our lmdb.h version field says 0.9.90, which probably means we just got the master branch from github at some point? We're thinking to either downgrade to the official 0.9.35 tag or to upgrade to 1.0.0.
Yeah, that was your biggest mistake. "0.9.90" wasn't an actual version, it was just a placeholder in the development branch. It is definitely not production-quality code.
At this point we're about to release v0.9.36 and v1.0.1. You could use either the mdb.RE/0.9 or mdb.RE/1.0 branches instead of whatever you grabbed before. There's one relevant bugfix for Windows (ITS#10538) that you might want, otherwise 0.9.35 would be good enough for you.