From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christoph Scholtes Newsgroups: gmane.emacs.devel Subject: Re: bug#12007: 24.1.50; Crash in auto-revert-handler Date: Wed, 25 Jul 2012 05:34:32 -0600 Message-ID: <500FD9C8.7080705@gmail.com> References: <86pq7p8d9o.fsf@googlemail.com> <83mx2t1aut.fsf@gnu.org> <500B2BB0.1000402@gmail.com> <500F4055.4080005@gmail.com> <500F5BD7.6050203@yandex.ru> <500F6DAE.9010207@gmail.com> <500F7930.3060100@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1343216102 10556 80.91.229.3 (25 Jul 2012 11:35:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 25 Jul 2012 11:35:02 +0000 (UTC) Cc: Eli Zaretskii , 12007@debbugs.gnu.org, Emacs development discussions To: Dmitry Antipov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 25 13:35:00 2012 Return-path: Envelope-to: ged-emacs-devel@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 1Stzrj-0005yB-Tx for ged-emacs-devel@m.gmane.org; Wed, 25 Jul 2012 13:34:56 +0200 Original-Received: from localhost ([::1]:33511 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Stzri-0007H2-TT for ged-emacs-devel@m.gmane.org; Wed, 25 Jul 2012 07:34:54 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:58265) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Stzrd-0007Gl-Cm for emacs-devel@gnu.org; Wed, 25 Jul 2012 07:34:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1StzrX-0001mR-PR for emacs-devel@gnu.org; Wed, 25 Jul 2012 07:34:49 -0400 Original-Received: from mail-gh0-f169.google.com ([209.85.160.169]:60211) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1StzrT-0001lp-Be; Wed, 25 Jul 2012 07:34:39 -0400 Original-Received: by ghrr18 with SMTP id r18so710540ghr.0 for ; Wed, 25 Jul 2012 04:34:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=n1lDlLZfXQkrh2hJOM3tVpZ60QmlPq6o0x+KvVejXhI=; b=zPaiE8KRkSOVjGcoCy3AjBTzbqA0WNX2LQnYGlXgwZQMgebMKnvuHnb2QJdQVM9mR6 BWJRfa2O+vSWYGlt6Zm5n2hqS6n0G8rSGYzTa8R822A1TUT/h57kqt6ySWkY0A7n26oU adSnOoo2i4SL0WhSFKiJlWQ/LVrAPH9ncmuWvdD0ulMBbRQEfuAYMoVbkjc40k8nEWow U4rW2BU5RTnWUF2UaI2YMqvC44fyDRLE/CPbzF1pKQ2DmDQZ5Iybio06rSZEwkBcUkBA G/hMToX8F0uV2zPC/gkegkNdNT2CxklRARaU4BJpc0d7fB9LhpIRSd6Yx0JIZ1t+LkFI i33A== Original-Received: by 10.42.19.131 with SMTP id c3mr23836608icb.36.1343216078630; Wed, 25 Jul 2012 04:34:38 -0700 (PDT) Original-Received: from [192.168.1.2] (174-29-198-31.hlrn.qwest.net. [174.29.198.31]) by mx.google.com with ESMTPS id bo7sm2099188igb.2.2012.07.25.04.34.35 (version=SSLv3 cipher=OTHER); Wed, 25 Jul 2012 04:34:37 -0700 (PDT) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: <500F7930.3060100@yandex.ru> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.160.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:151880 Archived-At: On 7/24/2012 10:42 PM, Dmitry Antipov wrote: >> One other thing to note. I have never seen this crash on GNU/Linux. >> I use Emacs all day at work on that platform and build from trunk >> every morning. Any idea why it would only happen on Windows? > > I'm not using Emacs on Windows, so I don't know exactly. But, kill-buffer > is (over?)complicated thing which depends on hooks installed, display > state, > processes under the buffer being killed, auto-save state, etc., and these > things may be slightly different under Windows. OK. I ran this instance over night and it is still running. Usually the crash happened after an hour or so. Can you apply this patch to the trunk?