From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Frame bugs hanging Emacs Date: Mon, 1 Feb 2010 02:36:55 +0100 Message-ID: References: <17C5A105DB034AAFBEE64E29A38561C9@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1264988253 9959 80.91.229.12 (1 Feb 2010 01:37:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Feb 2010 01:37:33 +0000 (UTC) Cc: Emacs-Devel devel To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 01 02:37:25 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NblEC-0006nb-Ma for ged-emacs-devel@m.gmane.org; Mon, 01 Feb 2010 02:37:24 +0100 Original-Received: from localhost ([127.0.0.1]:55358 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NblEB-0006YZ-Qe for ged-emacs-devel@m.gmane.org; Sun, 31 Jan 2010 20:37:23 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NblE5-0006YU-LC for emacs-devel@gnu.org; Sun, 31 Jan 2010 20:37:17 -0500 Original-Received: from [199.232.76.173] (port=33722 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NblE5-0006YM-8r for emacs-devel@gnu.org; Sun, 31 Jan 2010 20:37:17 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NblE4-000305-Au for emacs-devel@gnu.org; Sun, 31 Jan 2010 20:37:17 -0500 Original-Received: from mail-fx0-f216.google.com ([209.85.220.216]:39164) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NblE4-0002zv-0w for emacs-devel@gnu.org; Sun, 31 Jan 2010 20:37:16 -0500 Original-Received: by fxm8 with SMTP id 8so4244664fxm.26 for ; Sun, 31 Jan 2010 17:37:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=T/GUB8Z0FN6dyr63vQTTkQC0NwIC5pWSBJCu9UoCuvs=; b=c0/cCnoZql55kv4ITNfCgkld5UTlrhMhxThhmlt7CooacGaZ6NQCeuuo0xsKbmRzal VpQMBbpc4opVgJlahuzcRQTEgTdb2V1n/ojk2h3emGpI05co56Ps3i0oIuRMoDrZWioc skrTPA3GgvuHuGxIvEQDFtONgq1vbwBqwAYng= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Gb0ni4RXK4KvuIsnETrPa5923qs2mEdEpahWZZw2HdfxHGRanwJcxm+L4bROvZb4gZ 6FBqoKRH7W1UTFGmRwS99mUwMKJ5LXcPMhVbNrrXxbJWIUVhIlXpKH0B8RIGF44C+j92 x57Nvb0P3xAw777CbUyuhruvUQVDVzLT1mJig= Original-Received: by 10.239.146.210 with SMTP id x18mr65075hba.77.1264988235168; Sun, 31 Jan 2010 17:37:15 -0800 (PST) In-Reply-To: <17C5A105DB034AAFBEE64E29A38561C9@us.oracle.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:120763 Archived-At: On Mon, Feb 1, 2010 at 2:31 AM, Drew Adams wrote: >> I just hit one of those frame bugs on w32 I have reported previously >> some times. This time it hanged a bit worse than before. Emacs is not >> looping, but it is hanging so badly I can't even kill the process. >> >> I can't remember I have seen this before. Anyone have any idea of what >> kind of hang this is? >> >> It looks like a hang in the app w32 message queue function, but I >> thought messages to kill the process bypassed this local queue. > > M-x report-emacs-bug > > (You don't even say what Emacs version you're using.) Thanks, but I have reported rather similar bugs many times. Without getting any comments on the bug reports. There is something seriously wrong with frame creation on w32, but none of us have looked into it yet. This was probably just another variant of the bug. But it may be an important piece of info, perhaps, of course.