From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.bugs Subject: bug#12832: 24.3.50; Emacs lockup when idle Date: Tue, 13 Nov 2012 16:00:30 +0000 Message-ID: <50A26E9E.4020405@gmail.com> References: <838vac12kn.fsf@gnu.org> <509BFAE7.8020205@gmail.com> <83liebyu9t.fsf@gnu.org> <509CDF7F.2000409@gmail.com> <83ip9fyqmy.fsf@gnu.org> <83390izlxm.fsf@gnu.org> <509D4DAC.1060901@gmail.com> <83pq3hvet0.fsf@gnu.org> <509BAC2E.2000702@gmail.com> <80r4nxsl1s.fsf@somewhere.org> <83lie5vbot.fsf@gnu.org> <50A2585A.3050008@gmail.com> <83ip99v8h5.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1352822503 20815 80.91.229.3 (13 Nov 2012 16:01:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Nov 2012 16:01:43 +0000 (UTC) Cc: fni@missioncriticalit.com, 12832@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 13 17:01:50 2012 Return-path: Envelope-to: geb-bug-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 1TYIvt-00039e-Qk for geb-bug-gnu-emacs@m.gmane.org; Tue, 13 Nov 2012 17:01:50 +0100 Original-Received: from localhost ([::1]:43480 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TYIvk-0000XD-8h for geb-bug-gnu-emacs@m.gmane.org; Tue, 13 Nov 2012 11:01:40 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:34884) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TYIve-0000Wb-NA for bug-gnu-emacs@gnu.org; Tue, 13 Nov 2012 11:01:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TYIvb-0001Rj-Ks for bug-gnu-emacs@gnu.org; Tue, 13 Nov 2012 11:01:34 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56854) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TYIvb-0001Rf-HB for bug-gnu-emacs@gnu.org; Tue, 13 Nov 2012 11:01:31 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TYIw5-0000wJ-LT for bug-gnu-emacs@gnu.org; Tue, 13 Nov 2012 11:02:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Andy Moreton Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 13 Nov 2012 16:02:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 12832 X-GNU-PR-Package: emacs,w32 X-GNU-PR-Keywords: Original-Received: via spool by 12832-submit@debbugs.gnu.org id=B12832.13528224753558 (code B ref 12832); Tue, 13 Nov 2012 16:02:01 +0000 Original-Received: (at 12832) by debbugs.gnu.org; 13 Nov 2012 16:01:15 +0000 Original-Received: from localhost ([127.0.0.1]:38872 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TYIvH-0000vH-8i for submit@debbugs.gnu.org; Tue, 13 Nov 2012 11:01:15 -0500 Original-Received: from mail-wi0-f180.google.com ([209.85.212.180]:36269) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TYIvB-0000v3-9D for 12832@debbugs.gnu.org; Tue, 13 Nov 2012 11:01:10 -0500 Original-Received: by mail-wi0-f180.google.com with SMTP id x18so1050054wia.15 for <12832@debbugs.gnu.org>; Tue, 13 Nov 2012 08:00:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.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=CmWY6s+fxF5lm+tnkGKNvDE5B76f4CzpIY5yYklp5Ks=; b=07o/l2OmmTluuMOnqfan3sPfpVtsw0EuxlmpjioMttD8WUTVzVQeefCnl8sAS8LxLl afNMARWjBpSaWa9Ty2Qe3YGp5xTw8lDWhm8Owl1k1Z+Wpx49ynRxAVe/Kl7/NEuc31r7 mKOhFWbHca0ZL+SPm9SxyEjCpITvOxdzOjz/WiE/Wc4mpNkLavy8fTWXLuDci7Va9Nwd 9XN1O/3WnBPtSsfdc39/S1g4pfzuhQT2yWILCtQNLDvQUMR/FVPhPLq7V8c2PsmWqPBN pF1WTitGIr1nhIRjKX+l5LqwAMf6O+smm0xQxLW5tyF+0HSxJpyGW1C55vFnZKewoX4c LMSA== Original-Received: by 10.180.88.100 with SMTP id bf4mr2656863wib.16.1352822433915; Tue, 13 Nov 2012 08:00:33 -0800 (PST) Original-Received: from [10.17.20.82] (uk.solarflare.com. [193.34.186.16]) by mx.google.com with ESMTPS id b1sm3610169wix.11.2012.11.13.08.00.32 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Nov 2012 08:00:33 -0800 (PST) User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 In-Reply-To: <83ip99v8h5.fsf@gnu.org> X-Spam-Score: 0.1 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-Spam-Score: -0.7 (/) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 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.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:66875 Archived-At: On 13/11/2012 15:16, Eli Zaretskii wrote: >> Date: Tue, 13 Nov 2012 14:25:30 +0000 >> From: Andy Moreton >> CC: Dani Moncayo , fni@missioncriticalit.com, >> 12832@debbugs.gnu.org >> >> Correct - I've done a clean bootstrap using 4.7.0, and I see this problem on >> both trunk and emacs-24 branches. >> >> Looking emacs-24 (r110863) with Process Explorer: >> >> 212412 emacs.exe+0x32291 State: Wait:DelayExecution >> 212616 emacs.exe+0x148efe State: Wait:Suspended >> 212604 emacs.exe+0x142350 State: Wait:WrUserRequest >> 236140 RPCRT4.dll!ThreadStartRoutine State: Wait:WrQueue >> >> I tried suspending and then resuming each thread in turn from Process >> Explorer. Resuming thread 212604 unblocked emacs and it started working again. > > Was that the only thread whose resumption unlocks Emacs? If so, can > you find out what thread was that? Process Explorer can show that > call-stack, and you should be able to find out what functions were I tried to get call stacks from process Explorer, but that made it die :-( The fatc that thread 236140 is at ThreadStartRoutine makes me wonder if this is related to the perils of DllMain (i.e. the loader lock). > If you attach GDB, do you again see garbled backtrace, like in the > original report? Or do you see something more informative? Sorry, I don't have the original process running any more - it's hard to get anything done with an unresponsive app of the screen. I'll try to dig out more info the next time I get a lockup. The one thing that does seem completely consistent is that the lockup happens after several minutes of being idle (i.e. no keyboard or mouse input). AndyM