all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: 48884@debbugs.gnu.org
Subject: bug#48884: 28.0.50; Possible memory leak in window-text-pixel-size (bidi cache)
Date: Mon, 07 Jun 2021 15:04:28 +0300	[thread overview]
Message-ID: <83im2phodv.fsf@gnu.org> (raw)
In-Reply-To: <m1k0n6fzbu.fsf@yahoo.es> (bug-gnu-emacs@gnu.org)

> Date: Sun, 06 Jun 2021 23:38:45 +0200
> From:  Daniel Martín via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 
> I'm investigating how Emacs handles memory and I think I've found a
> memory leak in window-text-pixel-size.  This function is called by
> minibuffer completion packages like selectrum or vertico, so even if
> each leak is around 7,5 KB per minibuffer interaction on my system,
> users interact a lot with the minibuffer in a typical Emacs session, so
> the amount of leaked memory may be substantial if an Emacs session spans
> weeks.
> 
> I don't have a minimum program to reproduce it yet, but here's what I see
> when I trace the code when I use one of the aforementioned packages:

You are right, should be fixed now.

Thanks.





  reply	other threads:[~2021-06-07 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1k0n6fzbu.fsf.ref@yahoo.es>
2021-06-06 21:38 ` bug#48884: 28.0.50; Possible memory leak in window-text-pixel-size (bidi cache) Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-07 12:04   ` Eli Zaretskii [this message]
2021-06-09 10:36     ` Lars Ingebrigtsen
2021-06-09 11:52       ` Eli Zaretskii
2021-06-13  0:43         ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-13  6:32           ` Eli Zaretskii
2021-06-08  3:56   ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83im2phodv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48884@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.