From: Joseph Mingrone <jrm@ftfl.ca>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs memory management and sluggishness
Date: Wed, 31 Jul 2019 19:27:06 -0300 [thread overview]
Message-ID: <86y30dkfgl.fsf@phe.ftfl.ca> (raw)
In-Reply-To: <87a7ctrgn2.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Thu, 01 Aug 2019 00:19:45 +0200")
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
Óscar Fuentes <ofv@wanadoo.es> writes:
> 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.
I just tried it again and held down 'n' to visit all pages and the
memory stayed under 500 MB. I am using pdf-tools v0.90. I also just
tried with
https://file-examples.com/wp-content/uploads/2017/10/file-example_PDF_1MB.pdf
and the memory stayed under 400 MB. I'm somewhat confident that I
encountered memory issues in an Emacs instance without visiting a PDF
file.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 979 bytes --]
next prev parent reply other threads:[~2019-07-31 22:27 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
2019-07-31 22:27 ` Joseph Mingrone [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y30dkfgl.fsf@phe.ftfl.ca \
--to=jrm@ftfl.ca \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.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.