unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joseph Mingrone <jrm@ftfl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: Emacs memory management and sluggishness
Date: Thu, 01 Aug 2019 06:46:13 -0300	[thread overview]
Message-ID: <86pnlpnrq2.fsf@phe.ftfl.ca> (raw)
In-Reply-To: <83zhkthagt.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 01 Aug 2019 05:43:14 +0300")

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Joseph Mingrone <jrm@ftfl.ca>
>> Date: Wed, 31 Jul 2019 19:27:06 -0300
>> Cc: emacs-devel@gnu.org

>> > 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.

> What image library is used for that?  Is it ImageMagick or is it
> something else?

From https://github.com/politza/pdf-tools

It uses poppler to render PDFs.  "...there is one feature (following
links of a PDF document by plain keystrokes) which requires
imagemagick’s convert utility."

When I woke this morning, memory usage went from about 200-300 MB to
about 3 GB overnight.  No PDFs were open.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 979 bytes --]

  reply	other threads:[~2019-08-01  9:46 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
2019-08-01  2:43                     ` Eli Zaretskii
2019-08-01  9:46                       ` Joseph Mingrone [this message]
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=86pnlpnrq2.fsf@phe.ftfl.ca \
    --to=jrm@ftfl.ca \
    --cc=eliz@gnu.org \
    --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 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).