From: Jean Louis <bugs@gnu.support>
To: edgar <edgarlux@cryptolab.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to debug memory leaks
Date: Thu, 25 Mar 2021 22:38:36 +0300 [thread overview]
Message-ID: <YFzmvJpmvz1ofy0O@protected.localdomain> (raw)
In-Reply-To: <8f819f0993f17fc2f826f385ef1331ce@cryptolab.net>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
* edgar <edgarlux@cryptolab.net> [2021-03-25 20:56]:
> From: Stefan Monnier
> > > So maybe that memory effects, whatever they are, leaking, plumbing,
> > > I do not observe it now, but who knows...
> >
> > Call it "excessive memory use". That term even has the advantage of
> > including a notion of personal judgment (in the term "excessive") which
> > indeed reflects the fact that maybe this is not the result of a bug, but
> > you still find it excessive (and other people may disagree without
> > making your judgment wrong since it's
> > just an opinion).
> >
>
> The risk of leaving an unfruitful discussion is to let others think that a
> point has been made which could possibly influence or confuse outsiders and
> have unexpected adverse consequenes.
>
> May be "management" is a better term, but obviously Stefan has a different
> idea of "leak" (I guess as related to memory injection--I don't know, and
> would not like to add yet another level of needless argument). I did write
>
> I think that it is leaking memory
>
> which implies that I did not know if that was certain. I apologise for any
> misconstrued conclusions from my statement
>
> It seems that font leaking is a common issue as well
>
> I meant that, in general terms, /font leaking has been found by other users
> to happen as well/. If by the end of:
I have 2 pictures attached on what happens sometimes on my side.
Is that maybe font leaking? It looks like some fonts leaked somewhere
and I don't know where... there is hole somewhere...
[-- Attachment #2: 2021-02-21-00:35:41a.png --]
[-- Type: image/png, Size: 247558 bytes --]
[-- Attachment #3: Screenshot-from-2021-03-14-11-02-46.png --]
[-- Type: image/png, Size: 67591 bytes --]
next prev parent reply other threads:[~2021-03-25 19:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 5:29 How to debug memory leaks edgar
2021-03-25 14:23 ` Stefan Monnier
2021-03-25 15:01 ` Jean Louis
2021-03-25 15:18 ` Stefan Monnier
2021-03-25 20:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 17:54 ` edgar
2021-03-25 18:26 ` Stefan Monnier
2021-03-25 19:38 ` Jean Louis [this message]
2021-03-25 22:24 ` edgar
2021-03-26 5:48 ` Robert Thorpe
2021-03-26 5:58 ` edgar
2021-03-26 14:11 ` Stefan Monnier
2021-03-26 14:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 14:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 14:57 ` Arthur Miller
2021-03-26 15:02 ` Eli Zaretskii
2021-03-26 15:09 ` Arthur Miller
2021-03-26 15:33 ` Eli Zaretskii
2021-03-26 15:53 ` Arthur Miller
2021-03-26 16:03 ` Eli Zaretskii
2021-03-26 16:11 ` Arthur Miller
2021-03-26 16:25 ` Stefan Monnier
2021-03-26 16:32 ` Arthur Miller
2021-03-26 16:44 ` Stefan Monnier
2021-03-26 18:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 18:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-27 8:20 ` Arthur Miller
2021-03-27 15:03 ` Stefan Monnier
2021-03-27 15:13 ` Arthur Miller
2021-03-27 15:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 15:10 ` boost interactive feel speed (was: Re: How to debug memory leaks) Emanuel Berg via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2021-03-25 22:21 How to debug memory leaks edgar
2021-03-21 18:17 edgar
2021-03-21 18:25 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YFzmvJpmvz1ofy0O@protected.localdomain \
--to=bugs@gnu.support \
--cc=edgarlux@cryptolab.net \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).