From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.help Subject: Re: emacs frame screws up now and then on Windows XP Date: Wed, 3 Feb 2010 19:07:04 +0100 Message-ID: References: <21gleil2517h.fsf@gmail.com> <83fx5igq4e.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1265220542 22555 80.91.229.12 (3 Feb 2010 18:09:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Feb 2010 18:09:02 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Feb 03 19:08:59 2010 Return-path: Envelope-to: geh-help-gnu-emacs@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 1Ncjet-0000h7-Ch for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Feb 2010 19:08:59 +0100 Original-Received: from localhost ([127.0.0.1]:38690 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ncjes-000344-RD for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Feb 2010 13:08:58 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NcjdP-0002XG-K6 for help-gnu-emacs@gnu.org; Wed, 03 Feb 2010 13:07:27 -0500 Original-Received: from [199.232.76.173] (port=46276 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NcjdO-0002Wo-Te for help-gnu-emacs@gnu.org; Wed, 03 Feb 2010 13:07:26 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NcjdN-0006IV-W7 for help-gnu-emacs@gnu.org; Wed, 03 Feb 2010 13:07:26 -0500 Original-Received: from gv-out-0910.google.com ([216.239.58.189]:62369) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NcjdN-0006HZ-Hl; Wed, 03 Feb 2010 13:07:25 -0500 Original-Received: by gv-out-0910.google.com with SMTP id c17so76377gvd.17 for ; Wed, 03 Feb 2010 10:07:24 -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 :content-transfer-encoding; bh=HMaI0XdKWRmJgC6ElYlzTiikEz/NgniJ+3vv8xoQQ20=; b=g9jAtJCsqrTCi79lqXKx6MU3mntpaqsWcJGXdCt2ArMy+8tqg8Caip63CZzHSjmpux bG/A4k5N/uF1Aq495eJB9ol/etQ3GSj/2IYqMx1eIP0YGit2/oNkKjFDuIY5/z22neyv YlCvRKuYCVu25mT5bdECXUqkzk0vidoMQ3Etg= 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:content-transfer-encoding; b=ZvGYsGtHSFkKnSdgX/71W29IgEJ604ntWDvdvAmTA0kcLIEZ1i6+XUYLctTCajePTc 0pP/JulHsgvSTqlTAZHz+9F0nld5SmKK1Z9c1j9wWiGGX7yPAiM0ghjjAJtWH4sew1Y5 D3J4prugsobcqadu+CE11RlWo/gettpuVKHNU= Original-Received: by 10.239.186.20 with SMTP id e20mr1061326hbh.137.1265220444217; Wed, 03 Feb 2010 10:07:24 -0800 (PST) In-Reply-To: <83fx5igq4e.fsf@gnu.org> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:71661 Archived-At: On Wed, Feb 3, 2010 at 6:56 PM, Eli Zaretskii wrote: >> From: William Xu >> Date: Wed, 03 Feb 2010 13:37:38 +0800 >> >> See the attached screenshot. =C2=A0Why does the emacs frame screw up now= and >> then? I only see this on Windows XP. =C2=A0When this happens, I have to >> restart emacs. > > Never saw anything like that. I have never seen anything like that either, but I have seen Emacs hanging and crashing. Most of the times I believe it has something to do with frame creation, but I also suspect process creation sometimes. I am just not sure what is happening. Most of the time it is hard to reproduce (though I think I have given some examples of more easily reproducible crashes too). Since the crashes mostly happens sometime after frame creation I have suspected that it is some lookup in the w32 message handling though it takes a lot of time to dig into it. I have also suspected some badly protected data with resulting data corruption. This is not easy either (especially since there is no good marking of which part of the code is run in which thread). Your example looks like data corruption of course. Have you noticed some special chain of events that leads to this state?