From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#70544: 30.0.50; The primitive-function "call-process-region" returns "internal error" and causes high cpu usage on win10 Date: Thu, 09 May 2024 10:16:12 +0300 Message-ID: <867cg38ngj.fsf@gnu.org> References: <86zftj2szq.fsf@gnu.org> <86r0ev2mms.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39181"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 70544@debbugs.gnu.org To: leuven65@gmail.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 09 09:17:01 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s4y1U-000A8i-M8 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 May 2024 09:17:00 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s4y1C-0004Ic-Ne; Thu, 09 May 2024 03:16:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s4y18-0004Hj-4K for bug-gnu-emacs@gnu.org; Thu, 09 May 2024 03:16:39 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s4y16-0004rj-MX for bug-gnu-emacs@gnu.org; Thu, 09 May 2024 03:16:37 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s4y1W-000722-GU for bug-gnu-emacs@gnu.org; Thu, 09 May 2024 03:17:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 09 May 2024 07:17:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70544 X-GNU-PR-Package: emacs Original-Received: via spool by 70544-submit@debbugs.gnu.org id=B70544.171523901027013 (code B ref 70544); Thu, 09 May 2024 07:17:02 +0000 Original-Received: (at 70544) by debbugs.gnu.org; 9 May 2024 07:16:50 +0000 Original-Received: from localhost ([127.0.0.1]:53535 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s4y1J-00071c-K0 for submit@debbugs.gnu.org; Thu, 09 May 2024 03:16:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39962) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s4y1F-00071T-Op; Thu, 09 May 2024 03:16:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s4y0k-0004mS-7u; Thu, 09 May 2024 03:16:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=QF6tP5LrzECtWKZCwKb+JqjbTsqo8fQlhzeWday9gi0=; b=jKLNa6dypHFT bwAo4Mo5N2pIYeEJga4RU/Tv0FxXIirl3ompmk7y+vF815zYKAH6ZwFb5uffoGbxfxxLcqD+e/MgJ cEfEtGS78TSVUsXj4SEloWuKPLuzadwgqD7K26JrA+SpNRAZQJfl5BtG9P5sMJd78hY190wPgC3W1 zjZMJr9iwzPYcwuWrq/DfQqOB6fWAOhppFyfXZx0L871v7t2rrTDp825AcPrd1Lf4MTffaRVlpCZt B18ifiXcY0CcUrnbCgC/WOLopdMcWtueF+k9Nw/xXSOV+RG98QQ4IgAEn7IXHP3ISZcoa6jbvOb6v DTZbWn+5Z20zXQwZWzrtZA==; In-Reply-To: <86r0ev2mms.fsf@gnu.org> (message from Eli Zaretskii on Wed, 24 Apr 2024 11:25:15 +0300) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:284722 Archived-At: tags 70544 moreinfo thanks Ping! Can anyone reproduce this and/or tell more about what gitk.exe wants and why it fails? If no additional information emerges in a two-weeks time, I will close this bug due to lack of sufficient information. > Cc: 70544@debbugs.gnu.org > Date: Wed, 24 Apr 2024 11:25:15 +0300 > From: Eli Zaretskii > > > From: leuven65 > > Date: Wed, 24 Apr 2024 10:12:10 +0200 > > Cc: 70544@debbugs.gnu.org > > > > I use the latest version > > "[[https://github.com/git-for-windows/git/releases/tag/v2.44.0.windows.1]]", > > in which "a couple of bugs that could cause Git Bash to hang in > > certain scenarios were fixed", it might cause the exit behavior of > > "gitk.exe" changed. > > > > The program gitk is "${git-installation-folder}/cmd/gitk.exe". > > > > The issue only pops up when I set "(setq-default shell-file-name "cmdproxy.exe")", if set to "bash.exe", no such > > problem. > > Maybe this gitk was supposed to be invoked only from the MSYS Bash? > If so, this is not really a problem with Emacs. > > > When the issue happens, emacs is not blocked, I can smoothly input > > in emacs, but the cpu usage of emacs is very high forever. As I > > built emacs without debug information, what I can see so far is that > > most of time seems to be spent on "MsgWaitForMultipleObjects". > > > > I use "shell-command" (M-!) to run "gitk.exe", the correct behavior is to run "gitk" and block emacs, or exit with > > error, in my case, it prints out error "(Shell command killed by signal internal error)" and cpu usage goes up. > > I guess these all are related to the fact that gitk is not a console > problem, but a GUI problem, and therefore should not be invoked from > shell-command, at least not safely. It was probably meant to be > invoked from a shell directly, and perhaps specifically from the MSYS > Bash which comes with Git for Windows. > > Bottom line: I'm not convinced this is an Emacs problem, and I still > don't understand why you gitk from Emacs in this manner. > > In any case, to do anything with this problem, we need either a way to > reproduce it on the system of one of our developers, or a detailed > information regarding the reasons why Emacs is spinning calling > MsgWaitForMultipleObjects. > > > >