From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: master f0ff20be51: * src/emacs.c (main): Improve accuracy of daemon warning message on PGTK. Date: Wed, 06 Apr 2022 23:16:56 -0400 Message-ID: References: <164921225790.11115.15669298143254852205@vcs2.savannah.gnu.org> <20220406023058.315C7C009A8@vcs2.savannah.gnu.org> <87ilrm9qa7.fsf@athena.silentflame.com> <87ilrlzqgu.fsf@yahoo.com> <87y20hhg5b.fsf@athena.silentflame.com> <87tub5y5l8.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7991"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Sean Whitton , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 07 05:17:57 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncIei-0001nA-9v for ged-emacs-devel@m.gmane-mx.org; Thu, 07 Apr 2022 05:17:56 +0200 Original-Received: from localhost ([::1]:38680 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ncIeg-00047Y-Ki for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Apr 2022 23:17:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35972) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ncIdt-0003Mg-MP for emacs-devel@gnu.org; Wed, 06 Apr 2022 23:17:05 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:3069) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ncIdp-0004oj-NL for emacs-devel@gnu.org; Wed, 06 Apr 2022 23:17:04 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id B5DC78027D; Wed, 6 Apr 2022 23:16:59 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id D54EB80300; Wed, 6 Apr 2022 23:16:57 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1649301417; bh=rhP0WDiHGVIqXrSE/HclddAlLTQOyw/rI+ubGr19j7E=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Y3a4K2Iod4rt0Wx+9SSHATNjC5a7WZz/vD2eNH+hUisDEVeFu5LH+g+wMNnW/bMqy 2r9JoMbRzdCvlAa+nAycEG/FW7F2cV47NPUQTz8mTjpJ+GE1sCNYiaWgj7IwL/iMGY xhArMtGedjf/IYLklCb8DKPy/f+BAogt0jMdgVHgNCXY/vUtH+8msrrcNOgu/3RfLd pUBlVDtVljHqufgrDkwczsFrm6mTmiDscK9D82T3kI8YIG87NM1sA1aV1iFBvXgwvt sQey6tfiMTO6OVDkp+wI16yZc6jRh1ashKgpmcAvqE+ljqmUG/tKoK/r+e//xaWPE6 MsmmuwiwhUbzw== Original-Received: from alfajor (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id A108E120810; Wed, 6 Apr 2022 23:16:57 -0400 (EDT) In-Reply-To: <87tub5y5l8.fsf@yahoo.com> (Po Lu's message of "Thu, 07 Apr 2022 10:45:07 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:287872 Archived-At: >> FWIW, I think "fundamental" is a bit strong here. I don't see any >> evidence that the design of the API makes it impossible. It seems more >> like a problem with the current implementation > I think the problem is quite fundamental to the current implementation > of GDK: Fundamental to the implementation means that it can be fixed without changing the design of the API ;-) > lots of stuff is left unfreed when a display is programmatically > disconnected as-is, and freeing even that typically requires a working > connection to the display server. Which is unattainable when a display > disconnects due to an IO error. I suspect it's worse than that, since "left unfreed" would just lead to memory leaks, which I suspect could be tolerable (and in any case much better than what we have now). Stefan