From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#12587: 24.2; Delayed startup, unresponsive Emacs in MS Windows when netlogon services is running in a domain Date: Mon, 08 Oct 2012 11:15:07 +0200 Message-ID: <83vcel495w.fsf@gnu.org> References: <5070027B.80105@uni-muenster.de> <83ehlb7b2z.fsf@gnu.org> <5071558A.3030202@uni-muenster.de> <83r4pa5yuz.fsf@gnu.org> <507293AC.8090901@uni-muenster.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1349687810 12960 80.91.229.3 (8 Oct 2012 09:16:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Oct 2012 09:16:50 +0000 (UTC) Cc: 12587@debbugs.gnu.org To: Mohammed Imaduddin Humayun Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Oct 08 11:16:55 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 1TL9SJ-00039u-8Z for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Oct 2012 11:16:55 +0200 Original-Received: from localhost ([::1]:36657 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TL9SC-0000WZ-QT for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Oct 2012 05:16:48 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:59960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TL9S5-0000Vt-KS for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2012 05:16:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TL9Rz-0001aQ-Bf for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2012 05:16:41 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:50521) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TL9Rz-0001aM-90 for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2012 05:16:35 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TL9SP-0007dh-Oj for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2012 05:17:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 08 Oct 2012 09:17:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 12587 X-GNU-PR-Package: emacs,w32 X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 12587-submit@debbugs.gnu.org id=B12587.134968778929325 (code B ref 12587); Mon, 08 Oct 2012 09:17:01 +0000 Original-Received: (at 12587) by debbugs.gnu.org; 8 Oct 2012 09:16:29 +0000 Original-Received: from localhost ([127.0.0.1]:60772 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TL9Rt-0007cr-1t for submit@debbugs.gnu.org; Mon, 08 Oct 2012 05:16:29 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:41672) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TL9Rq-0007cc-Bj for 12587@debbugs.gnu.org; Mon, 08 Oct 2012 05:16:27 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MBK00300HOXE600@a-mtaout20.012.net.il> for 12587@debbugs.gnu.org; Mon, 08 Oct 2012 11:15:17 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MBK0025CHPDQ7B0@a-mtaout20.012.net.il>; Mon, 08 Oct 2012 11:15:14 +0200 (IST) In-reply-to: <507293AC.8090901@uni-muenster.de> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:65374 Archived-At: > Date: Mon, 08 Oct 2012 10:49:48 +0200 > From: Mohammed Imaduddin Humayun > CC: Eli Zaretskii > > - Post startup, if w32-get-true-file-attributes is: > (a) nil: file operations are responsive albeit 3-4x slower > than when netlogon is not running i.e. not instantaneous. > (b) default: extremely sluggish response. File operations > (opening of files, filename autocomplete or dired etc.) each take 2-3 > minutes or more. Is this with the latest development snapshot? If not, please try with that, a lot has changed in that area lately. Also, what happens when w32-get-true-file-attributes is set to t? Is the behavior closer to the default value or to nil? > > http://alpha.gnu.org/gnu/emacs/windows/ > > > > First, please see if the same slow startup happens with the latest > > snapshot. If it does, I will give you instructions on what to do to > > investigate. > > > > Thanks > Yes, the same problem occurs with the latest alpha build > 'emacs-20120917-r110062'. OK. If you don't already have GDB for Windows, please install it from here: http://sourceforge.net/projects/mingw/files/MinGW/Extension/gdb/GDB-7.5/ (If you are not an experienced MinGW user, you might be better off installing GDB with mingw-get utility, which is mentioned on the above page, because mingw-get will automatically install any dependencies needed by GDB.) Once GDB is installed, please follow these steps: . Invoke Emacs . Use the Task Manager or some equivalent to find out the process ID of emacs.exe (not of runemacs.exe!), which is a number. Since you say the startup takes minutes, it shouldn't be a problem to do this and the next step while Emacs is still stuck in whatever it's doing at this stage. . Type from the cmd prompt "gdb -p PID" where PID is the process ID of emacs.exe, and hit Enter. GDB will attach to the running Emacs, stop it wherever it is, and show its prompt "(gdb)". . Type at GDB's prompt "thread apply all backtrace", and post here everything that GDB reports in response. . If you can, try these steps both before and after the welcome screen comes up, because it's possible that there's more than one place that is holding the startup. Thanks.