From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" Date: Wed, 01 Jan 2025 14:14:38 +0200 Message-ID: <86ttailoi9.fsf@gnu.org> References: <878qrxgg74.fsf@Phoenix> <864j2lnf1j.fsf@gnu.org> <87ldvvhhqo.fsf@localhost> <87frm3elkr.fsf@Phoenix> <878qrvhe0k.fsf@localhost> <86v7uzljc5.fsf@gnu.org> <87ldvug9a3.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3820"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 75209@debbugs.gnu.org, njackson@posteo.net To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 01 13:16:25 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tSxeD-0000pd-51 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 01 Jan 2025 13:16:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSxds-000316-Ia; Wed, 01 Jan 2025 07:16:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSxdr-00030v-8g for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 07:16:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tSxdq-0003AY-V4 for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 07:16:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=VOuFVlRMgVDkGE8pGRH7dS0Ke08IKBak1jHOYJ9naRk=; b=kVQF2ADXhovCleRC3Zoh1HlOGtWyNza7qBU8YrawHtF75+C81vIM2MF5czYiNzcilFfdnyyV1+5GPUFhBx7+XE/toTgxzwdWZB2ZJbtBXPpCpdOALGyGJcAsM3BqAcwPurLm6ajl8BuwdzA2DLvqyioV5JxUzb04nzszpC1oqq17NzaT48Vh/GAaOTtFtC6jvLFvKiPXmsRB1v3/cu7keF2QeWqveZqLzq6lzfvr3/y8Oy7bYCUaiZQb6ZROmSMyPeGWWdYJSnBIhEV7mtflqSu5pETudDgnYcgbHy5+AGUJSN+mqTk5eLPTOepHcVccbZ+2lPVbbQW7KfJz/Hpb9w==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tSxdq-0002Jf-9H for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 07:16:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 01 Jan 2025 12:16:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75209 X-GNU-PR-Package: emacs Original-Received: via spool by 75209-submit@debbugs.gnu.org id=B75209.17357337038476 (code B ref 75209); Wed, 01 Jan 2025 12:16:02 +0000 Original-Received: (at 75209) by debbugs.gnu.org; 1 Jan 2025 12:15:03 +0000 Original-Received: from localhost ([127.0.0.1]:37937 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tSxcp-0002Bx-EH for submit@debbugs.gnu.org; Wed, 01 Jan 2025 07:15:02 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45682) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tSxcn-0002Bh-38 for 75209@debbugs.gnu.org; Wed, 01 Jan 2025 07:14:57 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSxcg-0001HE-Cm; Wed, 01 Jan 2025 07:14:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=VOuFVlRMgVDkGE8pGRH7dS0Ke08IKBak1jHOYJ9naRk=; b=jgLEXo1eTMsD XBcF6kRZWIyvlWYIyR959JC4mQ7QX2JLWuzPAUWtRknuzLqRt0C9nb1HILb/RA+E6usmFierKVq7G K2AFrF9bMhTEpGm86Ukjbu+H/OwsBAQNGk3Pz5InBQgLeub6vXocVDhZoUHHbdrgqnkN8A43eu83E xVqQMm7FNZ/Qf9m5znDzpjdStj734hyAZW/z3qwjKWzI4iwT3Gm9BSlOKEXaeLofxpZELUoWfZhZQ bAGDjSq+8AFsziHHjedmcu2KQfiS4ZaaaRmWv05j0rRWu1TKVuOEGslIu0o3AYTkqnBYvzAIRqvD4 SOaWHYofxTTNV1d2FrLs3Q==; In-Reply-To: <87ldvug9a3.fsf@localhost> (message from Ihor Radchenko on Wed, 01 Jan 2025 09:42:28 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298063 Archived-At: > From: Ihor Radchenko > Cc: njackson@posteo.net, 75209@debbugs.gnu.org > Date: Wed, 01 Jan 2025 09:42:28 +0000 > > Eli Zaretskii writes: > > >> Another possible scenario is two Org instances writing to the same file > >> at the same time. > >> If it is what is happening in your case, your problem may be similar to > >> https://list.orgmode.org/orgmode/CAMJKaZxA_VmLdFP_u1rNiF2s0X2kVivjT31jEM_r3BYCHri1PQ@mail.gmail.com/ > > > > Can't Org prevent more than one session writing to this file? We have > > file locks which can be used here, I think. > > That's exactly the idea I am trying in the linked thread to address the > issue. > > It is not the biggest problem there though. The problem is when there is > a race between Emacs processes writing to the same file one after > another (without any locking). Contents of the file may then become > unexpected compared to other Emacs session. Is the gc-lock.eld file supposed to be a singleton across all the Emacs sessions? Earlier you said: > gc-lock.eld is a file used to flag that cache dir is being worked > on by multiple emacs instances. GC here refers to > garbage-collecting cache data. Can you tell more about the purpose and use of this file? What is written to it, and how is it supposed to be used after being written? And what bad things happen when the Lisp readers errors out because it is unable to read the data for some reason? I'm asking because I'd like to think about, and then suggest, some suitable solutions, but I don't want to suggest nonsensical ones. Thanks.