From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net, rcopley@gmail.com
Cc: 28268@debbugs.gnu.org
Subject: bug#28268: 26.0.50; (MS Windows) crash on C-g after closing Git GUI
Date: Tue, 29 Aug 2017 21:59:07 +0300 [thread overview]
Message-ID: <83k21m2oas.fsf@gnu.org> (raw)
In-Reply-To: <83mv6i2s8y.fsf@gnu.org> (message from Eli Zaretskii on Tue, 29 Aug 2017 20:33:49 +0300)
> Date: Tue, 29 Aug 2017 20:33:49 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 28268@debbugs.gnu.org
>
> > Date: Tue, 29 Aug 2017 20:25:52 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: rcopley@gmail.com, 28268@debbugs.gnu.org
> >
> > git-gui.exe is a GUI program, so it releases the shell and the shell
> > exits
>
> Correction: git-gui.exe launches wish and exits.
It looks like not entirely our problem, or not at all: Windows itself
thinks that the process is still running, although waiting on its
handle to become signaled exits immediately, something that should
never happen.
I installed a semi-kludgey workaround which seems to avoid spinning
the CPU in this obscure case. Please see that the problem is solved
on your systems as well.
next prev parent reply other threads:[~2017-08-29 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 21:10 bug#28268: 26.0.50; (MS Windows) crash on C-g after closing Git GUI Richard Copley
2017-08-29 15:18 ` Eli Zaretskii
[not found] ` <CAPM58oj8XRzUJpRtbB_TCYxsfaWncDjwnGqTg-FFo6w2P5m8Qw@mail.gmail.com>
2017-08-29 16:08 ` bug#28268: Fwd: " Richard Copley
2017-08-29 16:09 ` Richard Copley
2017-08-29 16:22 ` Richard Copley
2017-08-29 16:53 ` Eli Zaretskii
2017-08-29 16:38 ` Noam Postavsky
2017-08-29 16:48 ` Richard Copley
2017-08-29 17:14 ` Noam Postavsky
2017-08-29 17:25 ` Eli Zaretskii
2017-08-29 17:33 ` Eli Zaretskii
2017-08-29 18:15 ` Richard Copley
2017-08-29 19:00 ` Eli Zaretskii
2017-08-29 18:59 ` Eli Zaretskii [this message]
2017-08-29 19:02 ` Richard Copley
2017-08-29 19:28 ` Eli Zaretskii
2017-08-29 19:38 ` Richard Copley
2017-08-30 14:15 ` Eli Zaretskii
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=83k21m2oas.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28268@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=rcopley@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.