From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 34763@debbugs.gnu.org
Subject: bug#34763: 27.0.50; url-retrieve-synchronously misbehaves inside eldoc-documentation-function
Date: Fri, 15 Mar 2019 17:47:13 +0200 [thread overview]
Message-ID: <83r2b8ywam.fsf@gnu.org> (raw)
In-Reply-To: <26aa8637-18db-2551-bff8-41276f22732b@yandex.ru> (message from Dmitry Gutov on Fri, 15 Mar 2019 16:24:44 +0200)
> Cc: 34763@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 15 Mar 2019 16:24:44 +0200
>
> Sounds like an external library problem, maybe?
GnuTLS?
> > If you do the same from an interactive function, not from eldoc, does
> > the problem happen there as well?
>
> More or less. I managed to make it slower by ~20x as well.
>
> Try this:
>
> (defun silly-eldoc ()
> (let ((start (time-to-seconds)))
> (dotimes (i 10)
> (url-retrieve-synchronously "http://www.google.com")
> (message "try %i" i))
> (format "done in %f" (- (time-to-seconds) start))))
>
> (defun silly-command ()
> (interactive)
> (message "%s" (silly-eldoc)))
>
> (global-set-key (kbd "C-o") #'silly-command)
>
> Call the command a few time with C-o, it should run the timer and finish
> with calculation how much time it took to run the requests. Now:
>
> 1. Alternate between pressing C-o and C-g, with varying speeds.
>
> The goal is to see
>
> error in process filter: Transfer interrupted!
> error in process filter: url-http-generic-filter: Transfer interrupted!
>
> a few times.
>
> 2. Then see if C-o still runs to completion. If it does, and does not
> look slow enough, repeat 1.
So it sounds like quitting in the middle of a URL retrieval leaves
some leftovers that get in the way of additional retrieval attempts.
> BUT! I have tried to reproduce this slowdown behavior with a local
> server, and so far no luck. Ping to Google (or almost any other website)
> is 100ms from my current location, so maybe it makes a difference.
Maybe with a local server you aren't fast enough to interrupt the
transfer before it completes?
next prev parent reply other threads:[~2019-03-15 15:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 21:34 bug#34763: 27.0.50; url-retrieve-synchronously misbehaves inside eldoc-documentation-function Dmitry Gutov
2019-03-11 0:18 ` Dmitry Gutov
2019-03-11 14:30 ` Eli Zaretskii
2019-03-12 9:08 ` Dmitry Gutov
2019-03-12 15:02 ` Dmitry Gutov
2019-03-12 17:18 ` Eli Zaretskii
2019-03-12 17:44 ` Dmitry Gutov
2019-03-12 18:00 ` Eli Zaretskii
2019-03-12 20:05 ` Dmitry Gutov
2019-03-13 16:49 ` Eli Zaretskii
2019-03-15 14:24 ` Dmitry Gutov
2019-03-15 15:47 ` Eli Zaretskii [this message]
2019-03-15 16:07 ` Dmitry Gutov
2019-03-15 14:29 ` Dmitry Gutov
2019-03-15 15:49 ` Eli Zaretskii
2019-04-03 23:37 ` Dmitry Gutov
2019-04-04 13:04 ` Eli Zaretskii
2019-04-04 13:29 ` Dmitry Gutov
2019-04-04 14:36 ` Eli Zaretskii
2019-04-05 0:29 ` Dmitry Gutov
2019-04-05 6:14 ` Eli Zaretskii
2019-04-08 10:25 ` Dmitry Gutov
2019-04-08 15:20 ` Eli Zaretskii
2019-04-08 16:42 ` Dmitry Gutov
2019-04-08 17:13 ` Eli Zaretskii
2019-04-09 0:48 ` Dmitry Gutov
2019-04-09 6:34 ` Eli Zaretskii
2019-04-10 1:44 ` Dmitry Gutov
2019-04-10 15:46 ` Eli Zaretskii
2019-04-11 1:03 ` Dmitry Gutov
2019-04-11 7:59 ` Andreas Schwab
2019-04-11 13:08 ` Dmitry Gutov
2019-04-11 15:08 ` Dmitry Gutov
2019-04-11 16:22 ` Eli Zaretskii
2019-04-11 16:31 ` Dmitry Gutov
2019-04-13 0:44 ` Dmitry Gutov
2019-05-15 5:16 ` Lars Ingebrigtsen
2019-05-21 1:02 ` 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
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=83r2b8ywam.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34763@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 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).