That's good to know. Since we're completely in the dark on how to
produce a reliable test case that exercises this crash, the hope was
that fuzzing could inch us towards a solution.
There's also the problem that we're observing these crashes on Windows 7
and x86-64 (at least for now), as evidenced by this report:
Fuzzing on that platform is quite a bit more difficult since tooling is=20=
lacklustre. Furthermore, we can't really try fuzzing under WSL and=20
Windows 10, since LMDB also doesn't actually work well under WSL, due to
mmap on a 0-length file failing with ENOEXEC, also complicating things:
I'm not clear if Robins George (OP) observed this crash on a different
platform, perhaps they can confirm?
If fuzzing isn't a worthwhile exploration avenue, any suggestions for=20
what kind of tests might exercise a crash like this?