From: Eli Zaretskii <eliz@gnu.org>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: 23431@debbugs.gnu.org, larsi@gnus.org
Subject: bug#23431: 25.0.93; EWW hangs
Date: Wed, 04 May 2016 17:56:53 +0300 [thread overview]
Message-ID: <83a8k5kh1m.fsf@gnu.org> (raw)
In-Reply-To: <87zis6a5sm.wl-jch@pps.univ-paris-diderot.fr> (message from Juliusz Chroboczek on Wed, 04 May 2016 04:57:45 +0200)
> Date: Wed, 04 May 2016 04:57:45 +0200
> From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 23431@debbugs.gnu.org
>
> > If the OP agrees that the issue is solved on master, we can close the bug.
>
> Sure, I'm very grateful for the fix
Thanks, so is it okay to close the bug?
> (I'm impatiently waiting for it to migrate into the 25 branch).
It most probably never will.
> But what about the 6-second hang, which I can reproduce even with
> with shr-image-animate set to nil? Should decoding of large images
> happen asynchronously, or is shr not designed for that?
We don't have infrastructure for doing this asynchronously. If the
concurrency branch ever gets revived and merged, such jobs might be
good candidates for using that facility. Otherwise, no, it isn't
possible. It's not shr that is not designed for that, it's Emacs
itself.
next prev parent reply other threads:[~2016-05-04 14:56 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 3:29 bug#23431: 25.0.93; EWW hangs Juliusz Chroboczek
2016-05-03 14:25 ` Kaushal Modi
2016-05-03 14:26 ` Lars Ingebrigtsen
2016-05-03 15:57 ` Lars Ingebrigtsen
2016-05-03 16:20 ` Eli Zaretskii
2016-05-03 16:26 ` Lars Ingebrigtsen
2016-05-03 16:40 ` Eli Zaretskii
2016-05-03 17:04 ` Lars Ingebrigtsen
2016-05-03 17:13 ` Eli Zaretskii
2016-05-03 17:23 ` Lars Ingebrigtsen
2016-05-03 17:34 ` Eli Zaretskii
2016-05-03 17:37 ` Lars Ingebrigtsen
2016-05-03 17:39 ` Lars Ingebrigtsen
2016-05-03 17:41 ` Eli Zaretskii
2016-05-03 17:48 ` Lars Ingebrigtsen
2016-05-03 18:17 ` Lars Ingebrigtsen
2016-05-03 17:17 ` Eli Zaretskii
2016-05-03 17:24 ` Lars Ingebrigtsen
2016-05-03 17:40 ` Eli Zaretskii
2016-05-03 17:43 ` Eli Zaretskii
2016-05-03 17:47 ` Lars Ingebrigtsen
2016-05-03 18:17 ` Lars Ingebrigtsen
2016-05-03 18:33 ` Eli Zaretskii
2016-05-03 16:26 ` Juliusz Chroboczek
2016-05-03 16:27 ` Lars Ingebrigtsen
2016-05-03 16:57 ` Eli Zaretskii
2016-05-03 18:51 ` Glenn Morris
2016-05-03 19:05 ` Lars Ingebrigtsen
2016-05-03 19:16 ` Glenn Morris
2016-05-03 19:23 ` Lars Ingebrigtsen
2016-05-03 20:10 ` Juliusz Chroboczek
2016-05-03 19:31 ` Eli Zaretskii
2016-05-03 19:37 ` Lars Ingebrigtsen
2016-05-04 2:34 ` Eli Zaretskii
2016-05-04 15:07 ` Lars Ingebrigtsen
2016-05-04 15:24 ` Eli Zaretskii
2016-05-03 20:25 ` Lars Ingebrigtsen
2016-05-03 20:47 ` Lars Ingebrigtsen
2016-05-03 20:53 ` Lars Ingebrigtsen
2016-05-03 21:34 ` Andreas Schwab
2016-05-03 23:37 ` Lars Ingebrigtsen
2016-05-04 2:45 ` Eli Zaretskii
2016-05-04 2:57 ` Juliusz Chroboczek
2016-05-04 14:56 ` Eli Zaretskii [this message]
2016-05-04 15:13 ` Nicolas Richard
2016-05-04 15:28 ` Eli Zaretskii
2016-05-04 15:26 ` Juliusz Chroboczek
2016-05-04 15:55 ` Eli Zaretskii
2016-05-04 15:10 ` Lars Ingebrigtsen
2016-05-04 15:16 ` Lars 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=83a8k5kh1m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23431@debbugs.gnu.org \
--cc=jch@pps.univ-paris-diderot.fr \
--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).