From: dick <dick.r.chiang@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45907@debbugs.gnu.org
Subject: bug#45907: [PATCH] Shr memory singularity gif89a
Date: Tue, 19 Jan 2021 11:53:16 -0500 [thread overview]
Message-ID: <87eeig50n7.fsf@dick> (raw)
In-Reply-To: <87v9bto4dg.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 19 Jan 2021 06:57:47 +0100")
LI> curl
LI> "https://raw.githubusercontent.com/enphysoft/search-gmail-using-message-id/main/images/lgmid.gif"
LI> > /tmp/lgmid.gif emacs -Q /tmp/lgmid.gif
This does not reproduce the error because it doesn't hit `shr-put-image` nor
`insert-image`. The error that I saw was memory being consumed *without limit*.
next prev parent reply other threads:[~2021-01-19 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 23:17 bug#45907: [PATCH] Shr memory singularity gif89a dick
2021-01-18 10:45 ` Robert Pluim
2021-01-19 5:57 ` Lars Ingebrigtsen
2021-01-19 16:53 ` dick [this message]
2021-01-19 17:47 ` Lars Ingebrigtsen
2021-01-19 23:27 ` dick
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=87eeig50n7.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=45907@debbugs.gnu.org \
--cc=larsi@gnus.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).