From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: {file} "locked by ... pid NNN", but there is no process NNN Date: Tue, 19 Jan 2016 20:01:53 +0200 Message-ID: <83lh7lbg8e.fsf@gnu.org> References: <2a0feba2-1cf6-498f-bbea-7fca8ce5d56e@googlegroups.com> NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453226538 23684 80.91.229.3 (19 Jan 2016 18:02:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Jan 2016 18:02:18 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 19 19:02:18 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aLabf-0007Ki-Cn for geh-help-gnu-emacs@m.gmane.org; Tue, 19 Jan 2016 19:02:15 +0100 Original-Received: from localhost ([::1]:38657 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLabe-0004pE-Sx for geh-help-gnu-emacs@m.gmane.org; Tue, 19 Jan 2016 13:02:14 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49780) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLabM-0004ho-Q6 for help-gnu-emacs@gnu.org; Tue, 19 Jan 2016 13:02:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLabH-0007V2-3z for help-gnu-emacs@gnu.org; Tue, 19 Jan 2016 13:01:56 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34907) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLabH-0007TN-0T for help-gnu-emacs@gnu.org; Tue, 19 Jan 2016 13:01:51 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2251 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aLabA-0004oz-2D for help-gnu-emacs@gnu.org; Tue, 19 Jan 2016 13:01:45 -0500 In-reply-to: (message from djc on Tue, 19 Jan 2016 02:40:21 -0800 (PST)) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:108786 Archived-At: > Date: Tue, 19 Jan 2016 02:40:21 -0800 (PST) > From: djc > Injection-Date: Tue, 19 Jan 2016 10:40:22 +0000 > > The situation was too complex and too intermittent to simplify easily for diagnosis, but I think I know generally what's happening: emacs is failing to delete its own lock of a file that I was working on once, but either (1) whose buffer has been killed or (2) where the lock has survived exiting and re-opening emacs. This never happens to me, except if my system crashes in the middle of editing a file. I have just searched my entire filesystem for user-lock files, and found none. This is my main development machine where a large Emacs session runs for weeks on end, in which I edit hundreds of files. If something like that was happening even with a small probability, I should have had several such files around. But I don't. > On Windows, emacs also doesn't necessarily release Windows handles of files and directories for which it no longer has any associated buffer. I've seen this repeatedly. In what Emacs version is that, in what version of Windows, and with what kind of filesystem (NTFS, FAT32, network)? I have here Emacs 24.5 on XPSP3 with NTFS volumes, which in this case runs for 11 days and 9 hours, and Process Explorer shows it holds a handle for a single directory -- my home directory -- and none of the almost 200 files this session visits. Of course, if you can at least describe under which circumstances these problems tend to happen, please do. And please report that using "M-x report-emacs-bug", not here. Thanks.