From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 19860@debbugs.gnu.org
Subject: bug#19860: 25.0.50; One url-retrieve-synchronously call running concurrently with another can freeze it
Date: Fri, 25 Dec 2015 19:34:09 +0100 [thread overview]
Message-ID: <87io3mxtr2.fsf@gnus.org> (raw)
In-Reply-To: <86bnkxnyju.fsf@yandex.ru> (Dmitry Gutov's message of "Sat, 14 Feb 2015 02:09:57 +0200")
Dmitry Gutov <dgutov@yandex.ru> writes:
> This applies both to master and emacs-24 (with a caveat).
>
> With sufficiently suitable server, calling long-ops-now or long-ops-idle
> can lead to the "outer" request never returning:
>
> (defun long-ops-idle ()
> (interactive)
> (run-with-idle-timer 0.2 nil #'long-outer-op)
> (run-with-idle-timer 0.5 nil #'long-inner-op))
>
> (defun long-ops-now ()
> (interactive)
> (run-with-timer 0.2 nil #'long-inner-op)
> (long-outer-op))
>
> (defun long-outer-op ()
> (message "retrieving outer")
> (url-retrieve-synchronously "http://localhost:9292")
> (message "outer retrieved"))
>
> (defun long-inner-op ()
> (message "retrieving inner")
> (url-retrieve-synchronously "http://localhost:9292")
> (message "inner retrieved"))
>
> The window freezes, the last message in the echo area being "inner
> retrieved" (but C-g breaks out of it, and if we're calling
> `long-ops-idle', the "outer" request succeeds, too).
It's unclear from the bug thread whether this is still a problem or
not... Are you still seeing this?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2015-12-25 18:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 0:09 bug#19860: 25.0.50; One url-retrieve-synchronously call running concurrently with another can freeze it Dmitry Gutov
[not found] ` <handler.19860.B.142387261510331.ack@debbugs.gnu.org>
2015-02-15 22:19 ` bug#19860: Acknowledgement (25.0.50; One url-retrieve-synchronously call running concurrently with another can freeze it) Dmitry Gutov
2015-02-16 1:00 ` Dmitry Gutov
2015-02-17 19:20 ` bug#19860: 25.0.50; One url-retrieve-synchronously call running concurrently with another can freeze it Glenn Morris
2015-02-17 23:24 ` Dmitry Gutov
2015-04-24 12:18 ` Dmitry Gutov
2015-04-25 23:19 ` Paul Eggert
2015-04-26 4:24 ` Dmitry Gutov
2015-04-26 4:30 ` Dmitry Gutov
2015-04-26 5:11 ` Paul Eggert
2015-04-26 15:28 ` Dmitry Gutov
2015-04-26 21:47 ` Paul Eggert
2015-04-26 15:01 ` Eli Zaretskii
2015-04-26 15:23 ` bug#19729: " Dmitry Gutov
2015-12-25 18:34 ` Lars Ingebrigtsen [this message]
2015-12-25 20:08 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io3mxtr2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19860@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.