From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Francesco Potortì" <pot@gnu.org>
Cc: John Wiegley <jwiegley@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
26952@debbugs.gnu.org
Subject: bug#26952: 25.1; loops eating all memory while yanking big rectangle
Date: Thu, 25 May 2017 13:42:39 -0400 [thread overview]
Message-ID: <CAM-tV-9s1VgwURDvmf3ZD=Hn=S6hs6FbCAPkKPWY4uyJASdmbA@mail.gmail.com> (raw)
In-Reply-To: <E1dDwaC-0004Rr-1g@tucano.isti.cnr.it>
On Thu, May 25, 2017 at 1:29 PM, Francesco Potortì <pot@gnu.org> wrote:
>>On Thu, May 25, 2017 at 12:48 PM, John Wiegley <jwiegley@gmail.com> wrote:
>>> FWIW, I too have noticed Emacs 25.2 being quite unstable. For the longest
>>> time, Emacs 24 would run for months without crashing even once. Now it crashes
>>> pretty regularly 2-4 times a day. I wonder now if I'm hitting a memory ceiling
>>> that is triggering the behavior we're describing...
>>
>>You're on macOS right? This bug and the proposed solution to be
>>backported only affects GNU/Linux distributions with recent glibc,
>>AFAIK.
>
> I'm on Debian. I'm curious to know what did I say to make you think I'm
> on Mac :)
"You're" was referring to John Wiegley there.
>
>>Also, I don't think this bug would trigger crashes, just extreme
>>system slowness due to swapping.
>
> Well, it eats all my memory. It is worse than a crash,
Yes, it can be. A crash only affects Emacs, the slowness affects the
whole system.
> the first time I
> had problems managing to kill Emacs.
Although as far as I could tell, a normal SIGINT is still enough to
kill Emacs, but it took around 10 or 20 seconds before it actually
took effect (due to the aforementioned system slowness).
next prev parent reply other threads:[~2017-05-25 17:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 14:53 bug#26952: 25.1; loops eating all memory while yanking big rectangle Francesco Potortì
2017-05-20 0:24 ` npostavs
2017-05-20 9:59 ` Eli Zaretskii
2017-05-20 17:41 ` npostavs
2017-05-20 17:59 ` Eli Zaretskii
2017-05-20 19:27 ` npostavs
2017-05-21 15:28 ` Eli Zaretskii
2017-05-21 16:00 ` npostavs
2017-05-21 16:10 ` Eli Zaretskii
2017-05-21 16:48 ` npostavs
2017-05-21 19:15 ` Paul Eggert
2017-05-21 19:53 ` Eli Zaretskii
2017-05-21 20:20 ` Paul Eggert
2017-05-21 20:40 ` npostavs
2017-05-21 20:40 ` Paul Eggert
2017-05-21 20:52 ` npostavs
2017-05-22 4:01 ` Eli Zaretskii
2017-05-25 5:31 ` John Wiegley
2017-05-25 15:09 ` Eli Zaretskii
2017-05-25 16:19 ` Paul Eggert
2017-05-25 16:41 ` Francesco Potortì
2017-05-25 17:20 ` Eli Zaretskii
2017-05-27 1:15 ` Glenn Morris
2017-05-27 6:57 ` Paul Eggert
2017-05-27 7:42 ` Eli Zaretskii
2017-05-25 16:48 ` John Wiegley
2017-05-25 17:18 ` Noam Postavsky
2017-05-25 17:29 ` Francesco Potortì
2017-05-25 17:42 ` Noam Postavsky [this message]
2017-05-25 17:45 ` Eli Zaretskii
2017-05-25 19:24 ` Paul Eggert
2017-05-25 19:34 ` Eli Zaretskii
2017-05-25 20:59 ` Paul Eggert
2017-05-26 6:25 ` Eli Zaretskii
2017-05-26 15:24 ` Paul Eggert
2017-05-21 20:06 ` npostavs
2017-05-22 3:58 ` Eli Zaretskii
2020-01-08 16:45 ` bug#26952: Possible regression of Bug#26952 - "repeated buffer insertion consumes excessive memory" Peter Ludemann
2020-01-09 0:08 ` bug#39045: Fwd: Possible regression " Peter Ludemann
2022-05-23 10:48 ` Lars Ingebrigtsen
2022-06-21 11:46 ` Lars Ingebrigtsen
2020-01-09 0:10 ` bug#26952: Possible regression of Bug#26952 " Peter Ludemann
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='CAM-tV-9s1VgwURDvmf3ZD=Hn=S6hs6FbCAPkKPWY4uyJASdmbA@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=26952@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jwiegley@gmail.com \
--cc=pot@gnu.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).