From: Antoine Levitt <antoine.levitt@inria.fr>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 25625@debbugs.gnu.org
Subject: bug#25625: Opening djvu file eats up all my RAM
Date: Thu, 7 Jun 2018 14:43:51 +0200 [thread overview]
Message-ID: <CABfD5m1khpC8o+jCrhiOuq8oGxMkOvXBhq5tpPzxvwWf+gkuJA@mail.gmail.com> (raw)
In-Reply-To: <87k1ra3jjz.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
With ulimit I get
libgomp: Thread creation failed: Resource temporarily unavailable
On Thu, 7 Jun 2018 at 13:47, Noam Postavsky <npostavs@gmail.com> wrote:
> tags 25625 + unreproducible
> quit
>
> Antoine Levitt <antoine.levitt@inria.fr> writes:
>
> > Standard imagemagick from linux mint 18.1:
> >
> > antoine@epsilon:~$ convert --version
> > Version: ImageMagick 6.8.9-9 Q16 x86_64 2016-11-29
> http://www.imagemagick.org
> > Copyright: Copyright (C) 1999-2014 ImageMagick Studio LLC
> > Features: DPC Modules OpenMP
> > Delegates: bzlib cairo djvu fftw fontconfig freetype jbig jng jpeg lcms
> lqr ltdl lzma openexr pangocairo png rsvg tiff wmf x xml zlib
>
> I'm not able to reproduce the problem, I can read the file you sent
> without trouble, albeit pretty slowly. It takes about ~15s to go to the
> next page, during which time I see (in top) Emacs' memory usage go up,
> but it goes back down again after the page is displayed. Perhaps the
> imagemagick version is the problem?
>
> ~$ convert --version
> Version: ImageMagick 6.9.7-4 Q16 x86_64 20170114
> http://www.imagemagick.org
> Copyright: © 1999-2017 ImageMagick Studio LLC
> License: http://www.imagemagick.org/script/license.php
> Features: Cipher DPC Modules OpenMP
> Delegates (built-in): bzlib djvu fftw fontconfig freetype jbig jng jp2
> jpeg lcms lqr ltdl lzma openexr pangocairo png tiff wmf x xml zlib
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
> COMMAND
> 23078 npostavs 20 0 1390832 831836 535952 D 42.9 20.9 2:08.71 emacs
> //{while going to next page}
> 23078 npostavs 20 0 679200 120040 26632 S 0.0 3.0 2:21.38 emacs
> //{after page is displayed}
>
> By the way (sorry I forgot to suggest this before asking you to retest)
> if you use ulimit to cap virtual mem at say 2GB 'ulimit -v $((2 * 1024
> 1024))' does Emacs give you an out of memory error instead of crashing
> your system?
>
[-- Attachment #2: Type: text/html, Size: 2668 bytes --]
next prev parent reply other threads:[~2018-06-07 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 8:50 bug#25625: Opening djvu file eats up all my RAM Antoine Levitt
2017-02-05 18:31 ` Eli Zaretskii
2017-02-05 18:35 ` Antoine Levitt
2017-02-05 19:40 ` Eli Zaretskii
2017-02-05 19:43 ` Antoine Levitt
2018-06-07 11:47 ` Noam Postavsky
2018-06-07 12:43 ` Antoine Levitt [this message]
2018-06-05 23:44 ` Noam Postavsky
2018-06-06 5:52 ` Antoine Levitt
2018-06-06 23:43 ` Noam Postavsky
2022-02-10 8:02 ` Lars Ingebrigtsen
2022-03-12 22:44 ` Lars Ingebrigtsen
2022-03-13 12:57 ` Antoine Levitt
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=CABfD5m1khpC8o+jCrhiOuq8oGxMkOvXBhq5tpPzxvwWf+gkuJA@mail.gmail.com \
--to=antoine.levitt@inria.fr \
--cc=25625@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/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).