From: Alcor via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "J.P." <jp@neverwas.me>
Cc: Alcor via General discussion about ERC <emacs-erc@gnu.org>,
69833@debbugs.gnu.org
Subject: bug#69833: 29.2; ERC 5.6-git: erc-dcc: Transmission of large (>500 MB) files hangs Emacs
Date: Sun, 17 Mar 2024 10:38:30 +0100 [thread overview]
Message-ID: <878r2hp59l.fsf__48985.8215952822$1710668387$gmane$org@tilde.club> (raw)
In-Reply-To: <871q89vi5o.fsf@neverwas.me> (J. P.'s message of "Sat, 16 Mar 2024 17:03:31 -0700")
"J.P." <jp@neverwas.me> writes:
> This sounds similar to:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54458
>
> If the solution from that bug doesn't suffice, can you provide an
> example (out of band if need be) of some file that induces this behavior
> when fetched?
>
> Thanks.
Yes, I can confirm the solution from that ticket (#54458) works. Using
"/dcc get -t", no problems are observed. Emacs remains responsive, and
the CPU usage during the transfer is slightly lower, too.
From what I understood, this is more of sender-specific issue, which is
well-known. Let me know if a reproducible example is still needed, I can
arrange something and send it off-list if necessary.
PS: Sorry for the noise, I did a debbugs search for "erc dcc" beforehand
but it yielded no results.
next prev parent reply other threads:[~2024-03-17 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 18:02 bug#69833: 29.2; ERC 5.6-git: erc-dcc: Transmission of large (>500 MB) files hangs Emacs Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 0:03 ` J.P.
[not found] ` <871q89vi5o.fsf@neverwas.me>
2024-03-17 9:38 ` Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <878r2hp59l.fsf@tilde.club>
2024-03-17 17:15 ` J.P.
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='878r2hp59l.fsf__48985.8215952822$1710668387$gmane$org@tilde.club' \
--to=bug-gnu-emacs@gnu.org \
--cc=69833@debbugs.gnu.org \
--cc=alcor@tilde.club \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
/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).