[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23842: 24.4; Runaway background process
From: |
Eli Zaretskii |
Subject: |
bug#23842: 24.4; Runaway background process |
Date: |
Sun, 26 Jun 2016 05:37:28 +0300 |
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sat, 25 Jun 2016 16:49:55 -0400
> Cc: Ian Perryman <iperryman@xtreme-eda.com>, 23842@debbugs.gnu.org
>
> On Sat, Jun 25, 2016 at 2:50 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Ian Perryman <iperryman@xtreme-eda.com>
> > With the current Emacs 25 pretest, this signals an error:
> >
> > Wrong type argument: window-live-p, #<window 7>
> >
> >> This will cause the emacs session to start using 100% of the CPU (you
> >> should have a top session running separately to notice. However this
> >> process is a background process and normal editing can continue until
> >> the process uses up all available memory. I kill it quickly using
> >> "C-g".
> >
> > Can someone reproduce this with the latest pretest of Emacs 25?
>
> I see the 100% CPU use in Emacs 24.5, but the window-live-p error in
> Emacs 25.0.95
Then I guess the problem was already fixed.
- bug#23842: 24.4; Runaway background process, Ian Perryman, 2016/06/24
- bug#23842: Dribble files, Ian Perryman, 2016/06/24
- bug#23842: 24.4; Runaway background process, Eli Zaretskii, 2016/06/25
- bug#23842: 24.4; Runaway background process, Paul Eggert, 2016/06/26
- bug#23842: 24.4; Runaway background process, Glenn Morris, 2016/06/26
- bug#23842: 24.4; Runaway background process, Ian Perryman, 2016/06/26
- bug#23842: 24.4; Runaway background process, Paul Eggert, 2016/06/26
- bug#23842: 24.4; Runaway background process, Ian Perryman, 2016/06/27
- bug#23842: 24.4; Runaway background process, Ken Brown, 2016/06/27
- bug#23842: 24.4; Runaway background process, Ian Perryman, 2016/06/27
- bug#23842: 24.4; Runaway background process, Eli Zaretskii, 2016/06/27
- bug#23842: 24.4; Runaway background process, Ken Brown, 2016/06/27
- bug#23842: 24.4; Runaway background process, Paul Eggert, 2016/06/26