On 1. Aug 2019, at 19:47, Howard Chu <hyc(a)symas.com> wrote:
> Hey folks.
> =3D46rom Myk=3DE2=3D80=3D99s investigations in the previous followup, =
> that the suggested changes to `mdb_cursor_init` to avoid using an
> invalid DBI might not be solving the actual issue, given the =
> of `mdb_page_search`.
Agreed, that assert that I suggested isn't catching what we want.
FWIW, here's my findings when attempting to look into what was happening =
with regards to that test case: =
It's unclear how much overlap there is with the previous findings, and =
whether or not calling `mdb_put` should assert with the DBI previously =
opened via `mdb_dbi_open` with MDB_CREATE. Let me know if what I'm =
observing here is expected.
> It=3DE2=3D80=3D99s also causing the seemingly correct test program to =
> when it wasn=3DE2=3D80=3D99t before. It=3DE2=3D80=3D99s unclear =
whether this should =3D
> be the case or not, perhaps Howard can confirm the expected =
> In any case, we=3DE2=3D80=3D99re wondering if there=3DE2=3D80=3D99s =
> progress, or if someone managed to reproduce this issue? Shipping
> features built on top of LMDB in Firefox is currently blocked due
> these failures, so any additional info would be helpful.
Sorry, still not seeing this over here. What else do you know about =
systems where this is occurring? RAM size, storage on HDD / SSD / USB
Here's everything we know about: =
0190324 See the "details" and "telemetry environment" sections for a
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/