From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jose A Ortega Ruiz Newsgroups: gmane.emacs.devel Subject: Re: Implementing image support for kitty terminal Date: Fri, 09 Sep 2022 06:48:52 +0100 Message-ID: <877d2dxfln.fsf@mail.jao.io> References: <87v8pz18wf.fsf@mail.jao.io> <83o7vrgimc.fsf@gnu.org> <87wnafdnee.fsf@logand.com> <835yhzgdyi.fsf@gnu.org> <87k06den1s.fsf@logand.com> <87illxy5ir.fsf@mail.jao.io> <87sfl1d1wi.fsf@logand.com> <87czc5y1wp.fsf@mail.jao.io> <8735d1cxrz.fsf@telefonica.net> 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="29138"; mail-complaints-to="usenet@ciao.gmane.io" To: =?utf-8?Q?=C3=93scar?= Fuentes , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 09 07:51:58 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 1oWWvm-0007Lj-24 for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Sep 2022 07:51:58 +0200 Original-Received: from localhost ([::1]:57698 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oWWvk-0005iA-DO for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Sep 2022 01:51:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39586) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWWsr-0004Ej-04 for emacs-devel@gnu.org; Fri, 09 Sep 2022 01:48:57 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46230) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWWsq-0007JW-5r; Fri, 09 Sep 2022 01:48:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=TkkAJkBKLWa/iXwHPlBqBlJlRTeytp3d1Uz8u9B26p8=; b=FlZCigZ6JmbLqvMZjPqg ot6yXFOJkMa+aDGMRjgjghU7dN/HKnrEjfCpBG1gP1MQD4k3yh4T2xud9AwR8KZaEupErvo0awjoQ 9pdjGMC2+UIARBSOAeIdYeqoyBOC5bvCFS04k419WyQxMgq0z6b1tjh6Yb09CW81Km1NK7KyCYNyY rfAVDlQhIn4qusgE3hBpdWmhaugZzOAX0nTOwQ0ZKuwR3NtGapEEJJdiUx2KlEzVlVtmuUOndkmag JW/SXIqf+KqpndaPbLaTNIRpHpAj98oLsbRv+Biu+qjOxGUyoPE4BykaAo8zOLq5jX6cQa0WhmwLv GpoxSWUUGnnKqQ==; Original-Received: from cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net ([92.233.85.247]:46058 helo=rivendell.localdomain) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oWWso-0007Pb-P3; Fri, 09 Sep 2022 01:48:54 -0400 Original-Received: from localhost (rivendell.localdomain [local]) by rivendell.localdomain (OpenSMTPD) with ESMTPA id 97c82bad; Fri, 9 Sep 2022 05:48:52 +0000 (UTC) In-Reply-To: <8735d1cxrz.fsf@telefonica.net> X-Attribution: jao X-Clacks-Overhead: GNU Terry Pratchett X-URL: 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:295033 Archived-At: On Fri, Sep 09 2022, =C3=93scar Fuentes wrote: > Jose A Ortega Ruiz writes: > >>> How is kitty not heavy-weight? >>> A graphical emacs already has all that. >> >> After 4-5 days of continous use, a graphical emacs is consuming around >> 2Gb for me, sometimes 3Gb; emacs-nox+kitty, combined, with the same >> workload except displaying images, is under 500Mb. foot is even >> slimmer. > > In my experience of many years, Emacs RSS usage stabilizes around ~500 > MB, which is what it is using right now in this box with M-x > emacs-uptime of 36 days. When it grows larger is because of some > extension eating memory or, more rarely, a bug in Emacs. > > Take a look at the output of M-x memory-report. > > If that is not enlightening, look for extensions that you use in GUI > Emacs and not in TUI Emacs, disable them and see if GUI Emacs' memory > keeps growing. thanks for your advice, but i've already tried all that and there's no obvious candidate. my conclusion is that it's the rendering to x surfaces that somehow is leaking memory, maybe when it refreshes, or colors or some other graphical resource (but not specially images, memory raises without displaying them). there is no extension that i don't use in one place and not the other, with the exception of doc-view, but i know it's not the cause because memory grows up in X even when i don't use it. likewise, i know gnus is not the cause, nor notmuch, because i see the effect with either. judging from your experience, it must be an external package that causes the leak, in graphical mode only, but i haven't been able to pinpoint one so far. perhaps i'll try with vertico/corfu next. all that said, i'd be a bit surprised if the leak came from a pure elisp package... thanks, jao --=20 The enjoyment of one's tools is an essential ingredient of successful work. =E2=80=93 Donald E. Knuth