From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>, 16587@debbugs.gnu.org
Subject: bug#16587: 24.3.50; max-specpdl-size exceeded + crash with gnus (shr).
Date: Thu, 13 Nov 2014 21:57:35 +0100 [thread overview]
Message-ID: <m3h9y2hl8g.fsf@stories.gnus.org> (raw)
In-Reply-To: <87k3df4zpt.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Fri, 31 Jan 2014 13:18:38 -0800")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Uhm. Bizarrely enough, I now get the max-specpdl-size exceeded message
> the first time I view the "HTML" message in question, but not subsequent
> times! (Per Emacs session.) That's totally weird.
Oh! I see! The first time I get the message, `max-specpdl-size' is
1300. Then each time I get it, it increases by 200, until it's finally
large enough at 2100 to descend that deep.
Is this by sneaky design?
Anyway, I still have no real idea as to how to handle this. Do a
stack-based "depth" investigation first to see how deep the DOM is, and
then refuse to render it if it's too deep?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2014-11-13 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 15:51 bug#16587: 24.3.50; max-specpdl-size exceeded + crash with gnus (shr) Nicolas Richard
2014-01-30 1:17 ` Katsumi Yamaoka
2014-01-30 11:56 ` Nicolas Richard
2014-01-31 2:25 ` Lars Ingebrigtsen
2014-01-31 2:37 ` Lars Ingebrigtsen
2014-01-31 2:46 ` Lars Ingebrigtsen
2014-01-31 14:28 ` Stefan Monnier
2014-01-31 21:21 ` Lars Ingebrigtsen
2014-01-31 15:00 ` Andy Moreton
2014-01-31 14:23 ` Stefan Monnier
2014-01-31 21:08 ` Lars Ingebrigtsen
2014-01-31 21:18 ` Lars Ingebrigtsen
2014-11-13 20:57 ` Lars Magne Ingebrigtsen [this message]
2014-11-13 21:13 ` Lars Magne Ingebrigtsen
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=m3h9y2hl8g.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=16587@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=theonewiththeevillook@yahoo.fr \
/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).