From: Eli Zaretskii <eliz@gnu.org>
To: dalanicolai <dalanicolai@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Question about (excessive?) ram usage when many overlays (with large vscroll)
Date: Tue, 26 Apr 2022 15:33:08 +0300 [thread overview]
Message-ID: <83zgk8kosb.fsf@gnu.org> (raw)
In-Reply-To: <CACJP=3miu=+qrqC+nQ-1RhzaDxrNWXP5e3dgd3ARr5+KphQJAw@mail.gmail.com> (message from dalanicolai on Tue, 26 Apr 2022 14:21:07 +0200)
> From: dalanicolai <dalanicolai@gmail.com>
> Date: Tue, 26 Apr 2022 14:21:07 +0200
>
> I have a question about ram usage when using overlays.
>
> So I have created `image-roll.el` for displaying documents/books (see here
> <https://lists.gnu.org/archive/html/emacs-devel/2022-04/msg00975.html>).
> However, I have just noticed that it uses a large amount of RAM when
> viewing (or
> trying to) pages in the back of 'large' books. But even if RAM usage still
> looks
> perfectly fine, Emacs crashes when trying to scroll to higher page numbers.
>
> I have looked a little into it, and have found that it is a consequence of
> using
> large overlays. There is no problem when creating a buffer containing many
> overlays, however, when trying to scroll to some overlay at the end of the
> buffer,
> Emacs will use huge amounts of RAM.
>
> So I am wondering if this is 'necessary' behavior; and then why is it
> necessary?
> The issue occurs even when displaying the same 'empty' svg-image on each
> overlay, but it occurs also when simply displaying some 'specified space' on
> each overlay.
I didn't yet try to reproduce this, but could you perhaps run this
test under GDB, and when Emacs crashes, show the C-level backtrace?
This could give good hints about the possible reason(s).
Thanks.
next prev parent reply other threads:[~2022-04-26 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 12:21 Question about (excessive?) ram usage when many overlays (with large vscroll) dalanicolai
2022-04-26 12:33 ` Eli Zaretskii [this message]
2022-04-26 13:24 ` Eli Zaretskii
2022-04-27 14:13 ` dalanicolai
2022-04-27 15:44 ` Eli Zaretskii
2022-04-27 17:13 ` Stefan Monnier
2022-04-27 17:18 ` Eli Zaretskii
2022-04-26 12:49 ` Po Lu
2022-04-27 14:01 ` dalanicolai
2022-04-28 11:56 ` dalanicolai
2022-04-28 12:06 ` Po Lu
2022-04-28 16:28 ` dalanicolai
2022-04-28 16:48 ` dalanicolai
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=83zgk8kosb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dalanicolai@gmail.com \
--cc=emacs-devel@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.
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).