Message-ID: <975893.96858.qm@web112413.mail.gq1.yahoo.com>
References: <3185EFAF9C8F7B4E9DBDF56829BF7C78290CBFA1@srv060ex01.ssd.fsi.com>
Date: Thu, 11 Feb 2010 09:39:10 -0800 (PST)
From: Stacey Campbell <staceycampbell@yahoo.com>
Subject: Re: emacs stalls using 100% CPU
To: cygwin@cygwin.com
In-Reply-To: <3185EFAF9C8F7B4E9DBDF56829BF7C78290CBFA1@srv060ex01.ssd.fsi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Tue, February 9, 2010 "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com> wrote:
> Intermittent problem.  It's happening more often again.
> NEW info, when top is run the memory columns (VIRT RES and SHR) data toggles
> Back and forth for COMMAND "emacs-X11" and "XWin".  See attached top log.
> The situation is recoverable with kill -9 of emacs-X11 process.

I have a couple of large Cygwin-X11 compiled X clients that sometimes start thrashing
the CPU when they should otherwise be blocked in a select()/poll() system call waiting
for socket or file I/O.  I haven't figured out any straightforward way to reproduce this
problem.  Maybe not coincidentally I see there are one or more outstanding poll()/select()
issues reported to this list recently...

Stacey


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple