[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
From: |
Michael Heerdegen |
Subject: |
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit |
Date: |
Tue, 26 Feb 2019 18:27:33 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Michael Heerdegen <michael_heerdegen@web.de> writes:
> > This isn't informative enough, I need a C-level backtrace plus a full
> > Lisp backtrace. Please next time attach a debugger when this happens,
> > source Emacs's src/.gdbinit, and type "thread apply all bt" at GDB
> > prompt.
>
> Ok, I'll do that.
This seems only to happen after several hours of suspended ram sleep. I
just waited this time to see if it ends, and after ~10 seconds, CPU
usage went to nearly zero and everything was good. I'm not sure if
Emacs is to blame for anything, though I didn't see this before. When
it happens the next time, I'll have a look if other programs are
responding.
Michael.
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, (continued)
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit,
Michael Heerdegen <=
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/26