https://bugs.openldap.org/show_bug.cgi?id=9378
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #14 from Howard Chu hyc@openldap.org --- Thanks to assistance from another user, we've made some progress setting up a KDE test environment to reproduce this issue. Using the replay logging facility in this branch https://git.openldap.org/hyc/openldap/-/tree/mplay09?ref_type=heads we collected a trace from one of the crash instances. The suspicious part is excerpted here:
mdb_put: 0x5638e7e58130, 2, 8[646f6d696e616e74], 16, 0 mdb_put: 0x5638e7e58130, 3, 8[646f6d696e616e74], 24, 0 mdb_put: 0x5638e7e58130, 2, 8[74656c6c74616c65], 8, 0 mdb_put: 0x5638e7e58130, 3, 8[74656c6c74616c65], 11, 0 mdb_put: 0x5638e7e58130, 2, 3[747874], 56200, 0 mdb_env_create: 0x559276b2ddc0 mdb_env_set_maxdbs: 0x559276b2ddc0, 12 mdb_env_set_mapsize: 0x559276b2ddc0, 274877906944 mdb_env_open: 0x559276b2ddc0, /home/vm/.local/share/baloo/index, 16793600, 0664 mdb_txn_begin: 0x559276b2ddc0, (nil), 0 = 0x559276b2f1c0 mdb_dbi_open: 0x559276b2f1c0, postingdb, 262144 = 2 mdb_dbi_open: 0x559276b2f1c0, positiondb, 262144 = 3 mdb_dbi_open: 0x559276b2f1c0, docterms, 262152 = 4 mdb_dbi_open: 0x559276b2f1c0, docfilenameterms, 262152 = 5 mdb_dbi_open: 0x559276b2f1c0, docxatrrterms, 262152 = 6 mdb_dbi_open: 0x559276b2f1c0, idtree, 262152 = 7 mdb_dbi_open: 0x559276b2f1c0, idfilename, 262152 = 8 mdb_dbi_open: 0x559276b2f1c0, documenttimedb, 262152 = 9 mdb_dbi_open: 0x559276b2f1c0, documentdatadb, 262152 = 10 mdb_dbi_open: 0x559276b2f1c0, indexingleveldb, 262152 = 11 mdb_dbi_open: 0x559276b2f1c0, failediddb, 262152 = 12 mdb_dbi_open: 0x559276b2f1c0, mtimedb, 262204 = 13 mdb_txn_commit: 0x559276b2f1c0 mdb_put: 0x5638e7e58130, 3, 3[747874], 91570, 0 mdb_put: 0x5638e7e58130, 2, 2[6368], 464, 0 mdb_put: 0x5638e7e58130, 3, 2[6368], 1286, 0 mdb_put: 0x5638e7e58130, 2, 7[766172696f7573], 1440, 0 mdb_put: 0x5638e7e58130, 3, 7[766172696f7573], 2282, 0
In the middle of txn 0x5638e7e58130 the init sequence occurs again, and all of the contents of this logfile are only being written by a single process. That means baloo_file has opened the same env twice in the same process, which is explicitly forbidden by the LMDB docs. http://www.lmdb.tech/doc/
Going to close this ticket as Invalid, it's a KDE bug and not an LMDB bug.