public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jan-Marek Glogowski <glogow@fbihome.de>
To: cygwin@cygwin.com
Subject: CPU hogging by dysfunctional bash or zsh when started via mintty Cygwin terminal link
Date: Fri, 14 Feb 2020 02:09:00 -0000	[thread overview]
Message-ID: <7c50f8ff-3eab-f226-7963-cd43478f68b5@fbihome.de> (raw)

Hi *,

I've already been on IRC (jmux) and had a longer debug session, trying
various stuff suggested by MetaNova. This is a Cygwin64 install.

Quoting from IRC: "After a longer time (probably months), I tried to
open a cygwin terminal, which now fails. It results in an empty window
with a blinking cursor and a bash process with 100% CPU load. The box is
a Windows 10 VM and also runs an cygwin openssh server, which I normally
use for development. SSH still works fine. I also installed gdb and
tried to attach to the CPU hogging bash, but I never see a gdb prompt
just some gdb startup output."

The condensed version, of what I already did and didn't change the result:

* updated cygwin install
* gdb -p <bash hog pid> -> hangs
  - killing bash will "start" gdb with the message, that the process
already exited
* starting zsh via the mintty link results in zsh hogging the CPU.
* cygwin.bat works; same for starting bash.exe from cmd
* reinstall mintty incl. "rebase-trigger fullrebase" didn't help
* strace mintty from a cygwin.bat shell results in a SIGSEGV
  - log currently at http://paste.debian.net/1130528/
  - expires: 2020-02-17 01:57:45
* gdb mintty results in ~ the same result, then gdb -p
  - it creates some threads, a bash hog window is created with all the
other "helpers" and gdb returns with "[Inferior 1 (<pid I guess)>)
exited with normally]" to the gdb prompt
  - quitting gdb and returning to the bash prompt won't happen, until I
kill the bash window, so basically the same, then doing "gdb -p"

This all looks like a mintty problem.

What else can I do to debug / fix this problem?

Regards,

Jan-Marek

P.S. Windows installed some updates today, but since I don't know when I
opened a terminal the last time, I can't tell if that is related.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2020-02-14  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14  2:09 Jan-Marek Glogowski [this message]
2020-02-14  2:40 ` Ken Brown
2020-02-14 11:47   ` Jan-Marek Glogowski

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=7c50f8ff-3eab-f226-7963-cd43478f68b5@fbihome.de \
    --to=glogow@fbihome.de \
    --cc=cygwin@cygwin.com \
    /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.
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).