From 4938d98f761a4fa12365613e904c924481a0c97d Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Wed, 10 Apr 2024 19:03:16 +0300 Subject: [PATCH] mu-indexer: re-enable database lock Seeing some db corruption; re-enabling this (old) lock to see if it helps. It _does_ slow down indexing significantly. --- lib/mu-indexer.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/mu-indexer.cc b/lib/mu-indexer.cc index 74808878..e7649337 100644 --- a/lib/mu-indexer.cc +++ b/lib/mu-indexer.cc @@ -242,8 +242,9 @@ Indexer::Private::add_message(const std::string& path) * but it believed those are _false alarms_ * https://gitlab.gnome.org/GNOME/glib/-/issues/2662 * - * std::unique_lock lock{w_lock_}; + * For now, set the lock as we were seeing some db corruption. */ + std::unique_lock lock{w_lock_}; auto msg{Message::make_from_path(path, store_.message_options())}; if (!msg) { mu_warning("failed to create message from {}: {}", path, msg.error().what());