all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>, 31179@debbugs.gnu.org
Subject: bug#31179: 26.1; eww leaves processes that slow Emacs
Date: Mon, 16 Apr 2018 22:19:41 +0200	[thread overview]
Message-ID: <87efjex5sy.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87po2ygbe7.fsf@gmail.com> (Alex Branham's message of "Mon, 16 Apr 2018 15:10:56 -0500")

Alex Branham <alex.branham@gmail.com> writes:

> Only slightly. It's at 0% before and at 1% after. The amount of time
> varies from anywhere between a quarter of a second to maybe 15 or 20
> seconds.
>
> Setting url-http-attempt-keepalives to nil as Andreas suggested seems to
> solve the problem.

Huh.  20 seconds is perhaps the time it takes for url to close the
connections normally?

But all this points to idle open connections slowing down your Emacs?
That's interesting...  and shouldn't happen.  How sluggish did this make
your Emacs?

The Emacs network connection code should be asynchronous and not lead to
any noticeable delays when you have idle connections, even if they're
TLS connections.  So it sounds like we might have an obscure bug
somewhere in that area?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2018-04-16 20:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 14:07 bug#31179: 26.1; eww leaves processes that slow Emacs Alex Branham
2018-04-16 14:20 ` Lars Ingebrigtsen
2018-04-16 14:25   ` Alex Branham
2018-04-16 14:25     ` Lars Ingebrigtsen
2018-04-16 14:29       ` Alex Branham
2018-04-16 14:33         ` Lars Ingebrigtsen
2018-04-16 20:10           ` Alex Branham
2018-04-16 20:19             ` Lars Ingebrigtsen [this message]
2018-04-16 14:23 ` Lars Ingebrigtsen
2018-04-16 15:08 ` Andreas Schwab

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=87efjex5sy.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=31179@debbugs.gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=schwab@suse.de \
    /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.