X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Authenticated: #19222419 Message-ID: <48CF7EFE.9070306@gmx.net> Date: Tue, 16 Sep 2008 11:40:14 +0200 From: Sybille Ebert User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygserver 1.5.25-15 slows down logoff References: <48BEB7F8 DOT 2080908 AT gmx DOT net> <48BF5B9D DOT 1010501 AT gmx DOT net> In-Reply-To: <48BF5B9D.1010501@gmx.net> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > My best guess would be that cygserver receives some sort of event that > causes it to wait/deadlock. I would really appreciate if someone could > look into what could be going wrong. I did some additional research. It seems that Windows in fact does send CTRL_LOGOFF_EVENT to a running service when the user is logging off. I am now reasonably sure that this is a bug in cygserver. The bug causes logoff event to be handled inappropriately. I am guessing SetConsoleCtrlHandler. The bug seems specific to x64. The problem only appears when a local user logs off, and not when remote desktop user logs off. I am really frustrated with logging off/shutdown taking up to 6 minutes. Unfortunately, my knowledge of Cygwin internals is extremely limited. If somebody could get me a good starting point, I am willing to look into it. S -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/