From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.devel Subject: Re: scratch/igc 7057c3562ff: * src/pgtkterm.c (mark_pgtkterm): Exclude from MPS builds. Date: Tue, 23 Jul 2024 05:34:06 +0000 Message-ID: References: <171946868539.21672.18232144356511203768@vcs2.savannah.gnu.org> <20240627061127.3F4BCC1FB5B@vcs2.savannah.gnu.org> <875xtuvrhp.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34884"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , emacs-devel@gnu.org, =?utf-8?Q?Gerd_M=C3=B6llmann?= , Eli Zaretskii To: Fejfighter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 23 12:58:08 2024 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 1sWDDb-0008t3-Ck for ged-emacs-devel@m.gmane-mx.org; Tue, 23 Jul 2024 12:58:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sWDBf-0007fd-44; Tue, 23 Jul 2024 06:56:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sW8AA-0002Kd-Nw for emacs-devel@gnu.org; Tue, 23 Jul 2024 01:34:14 -0400 Original-Received: from mail-40131.protonmail.ch ([185.70.40.131]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sW8A8-0002OQ-7K for emacs-devel@gnu.org; Tue, 23 Jul 2024 01:34:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1721712849; x=1721972049; bh=4BbGT0VK2jiLg371LO76JgKZP+OG/JdbUcf3ymobR8c=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=uFBSiECzauT3yvbboaAHH/SRdKgMmIk2x9CseBoPmk5IsF/bh1p507TxaGXxjermI Vz92fqfFjWdisUnZkFab2q0/gZvwJ/R+Q7DiJlY/8IvgX8YE4fxIuPROz0xEO7+NTH 46E8YbbbAWF7NnCchrfTH3w302doh1jj14uxT/LD/g8fk2kZr/19Mii480e4gft/3u gesdEuBqYzi8FPX5GHkHZt4kfnnCy6bxQEIjPN9Ay3o1c3liozK/leAGFQQX7QloLx Q5pxgyyKtGnXKwalrA9FSdIV2eF37GW5DZnpDbno5Zkp9eqohtiJFJQuae8PNVxbbM EwAqTghesemQQ== In-Reply-To: Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 30d626dd30c3a86c1a4a36b7fa4683743d9a3482 Received-SPF: pass client-ip=185.70.40.131; envelope-from=pipcet@protonmail.com; helo=mail-40131.protonmail.ch X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 23 Jul 2024 06:56:05 -0400 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:321978 Archived-At: On Tuesday, July 23rd, 2024 at 05:12, Fejfighter wro= te: > Comparing to xterm.c and scanning other parts of the pgtk specific code I= only found this as the only allocation unique to PGTK as much of the thing= s xterm needs to worry about is managed by gtk. Thanks! > Could someone apply this patch to the scratch/igc branch please? Will do. > I also ran the benchmark suite with the latest changes and it's the first= time that it has not crashed emacs/oom'd out or otherwise destabilized my = machine, > It is starting to appear to be more stable for my use cases That's great to hear! Running the benchmark suite should, of course, work. = However, performance can be improved a lot by playing with the relevant par= ameters, so the result might not be great yet :-) Also, there is a stability issue caused by signal handlers, which is fixabl= e. All the crashes I'm aware of that I haven't found another reason for are= due to that... Pip