From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs memory management and sluggishness
Date: Thu, 01 Aug 2019 00:19:45 +0200 [thread overview]
Message-ID: <87a7ctrgn2.fsf@telefonica.net> (raw)
In-Reply-To: <8636illum6.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Wed, 31 Jul 2019 19:14:25 -0300")
Joseph Mingrone <jrm@ftfl.ca> writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> Joseph Mingrone <jrm@ftfl.ca> writes:
>
>>> I am seeing even more aggressive memory usage with recent master branch
>>> commits (at least I think this only started in the last month or so).
>>> Here is a screenshot that shows over 3 GB of
>>> RSS. https://ftfl.ca/misc/emacs_memory.png
>
>>> This was running commit 06726f6 from today on 12.0-RELEASE-p8. I run
>>> Gnus, erc, look at an occasional PDF and edit text. I haven't visited
>>> any extremely large buffers recently. Garbage collection is happening,
>>> but it does not seem to help. But, when I call `garbage-collect'
>>> manually there will be a long pause if I haven't called it recently,
>>> then the memory will usually go down to something between 100 and 400
>>> MB.
>
>> Do the garbage collection, take note of the used memory, visit one of
>> those PDF files (preferably one with large, complex & colorful images)
>> move around for several pages and see if emacs' memory usage grows.
>
> It went from 440 to about 500 MB. This was a book with 1200
> pages and the PDF was about 3 MB.
How many pages of those 1200 you viewed? Do you use PDF-Tools or Doc
View? If you execute `garbage-collect' does the memory go down?
I'm asking all this because one of the possibilities is a leak on the
image handling code.
next prev parent reply other threads:[~2019-07-31 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 19:20 Emacs memory management and sluggishness Óscar Fuentes
2019-07-27 6:55 ` Eli Zaretskii
2019-07-27 12:36 ` Óscar Fuentes
2019-07-27 13:20 ` Eli Zaretskii
2019-07-27 23:52 ` Óscar Fuentes
2019-07-28 2:38 ` Eli Zaretskii
2019-07-31 20:54 ` Joseph Mingrone
2019-07-31 22:00 ` Óscar Fuentes
2019-07-31 22:14 ` Joseph Mingrone
2019-07-31 22:19 ` Óscar Fuentes [this message]
2019-07-31 22:27 ` Joseph Mingrone
2019-08-01 2:43 ` Eli Zaretskii
2019-08-01 9:46 ` Joseph Mingrone
2019-08-01 13:49 ` Eli Zaretskii
2019-08-10 2:28 ` Joseph Mingrone
2019-08-10 7:43 ` Eli Zaretskii
2019-08-11 20:30 ` Joseph Mingrone
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=87a7ctrgn2.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
--cc=jrm@ftfl.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).