From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes Date: Wed, 17 Feb 2016 22:02:14 +0200 Message-ID: <83d1rvumux.fsf@gnu.org> References: <23781.1455674752@allegro.localdomain> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1455739329 27681 80.91.229.3 (17 Feb 2016 20:02:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 17 Feb 2016 20:02:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: Mike Kupfer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 17 21:02:09 2016 Return-path: Envelope-to: ged-emacs-devel@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 1aW8Ia-0004Iu-Q5 for ged-emacs-devel@m.gmane.org; Wed, 17 Feb 2016 21:02:08 +0100 Original-Received: from localhost ([::1]:32896 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aW8Ia-0004FJ-4G for ged-emacs-devel@m.gmane.org; Wed, 17 Feb 2016 15:02:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52066) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aW8IW-0004F3-QZ for emacs-devel@gnu.org; Wed, 17 Feb 2016 15:02:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aW8IT-00080n-L0 for emacs-devel@gnu.org; Wed, 17 Feb 2016 15:02:04 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59663) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aW8IT-00080j-IE; Wed, 17 Feb 2016 15:02:01 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4876 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aW8IS-0002UU-Sb; Wed, 17 Feb 2016 15:02:01 -0500 In-reply-to: <23781.1455674752@allegro.localdomain> (message from Mike Kupfer on Tue, 16 Feb 2016 18:05:52 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:200093 Archived-At: > From: Mike Kupfer > cc: emacs-devel@gnu.org > Date: Tue, 16 Feb 2016 18:05:52 -0800 > > I ran "emacsclient -c" twice within a short period of time, and the > server log showed 2 frames being created. So *some* code in Emacs > thought the first frame was created, even though it didn't show up > in the output from (frame-list). This means Emacs started creating the frame, but didn't finish that process. A new frame is recorded in the frame list only when it is completely set up. The question is: what happens during that process which prevents it from completing? At this point, it looks like instrumenting x-create-frame to write traces to some file might tell what causes that function to stop doing its job half way through. > And I still think it's suspicious that the bad frame seems to match a > frame that was deleted earlier. Was the deleted frame deleted from the frame list?