From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Viet-Duc Le <vdle@protonmail.com>,
Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: xwin-xdg-menu high cpu usage with rxvt-unicode
Date: Wed, 23 Jun 2021 12:08:58 +0900 [thread overview]
Message-ID: <20210623120858.83e471aa7ddbc20cd41efb2c@nifty.ne.jp> (raw)
In-Reply-To: <tY-YzUNrM949zC_VJOeRHb8ZfRSYyZs8VHOJw5uBWmP-sdqzFXneuCcEBsv7N5906q8lQdA0SJXUz13FAv1uaTwY9inYMBGrwh1HHoHH1XA=@protonmail.com>
On Mon, 21 Jun 2021 05:49:28 +0000
Viet-Duc Le wrote:
> Hi,
>
> I've encountered a peculiar issue with rxvt-unicode launched from xwin-xdg-menu (20170321-1)
> The image below corresponds to two rxvt-unicode instances, each occupies 30% of system resouce.
> https://imgur.com/a/FTFwIrZ
> I'm using the the latest version of cygwin. 'cygcheck.out' is attached per guideline.
>
> Steps to reproduce:
> - Start XWin Server from Start menu
> - X applications menu -> System Tools -> rxvt-unicode
> - Kill rxvt-unicode to free the resource again
>
> Other observations:
> - XTerm does not incur high resources.
> - Manually launching rxvt-unicode from XTerm does not incur high resources.
>
> I think this is not an issue with rxvt but with xwin-xdg-menu.
> On laptop, it is very noticeable when the fan kicks in.
> Insights and suggestions are much appreciated.
>
> Thanks.
> Viet-Duc
I looked into this problem and found the cause.
urxvt seems to close stdout while xwin-xdg-menu use select()
to read stdout of the launched apps. Since stdout is closed,
select() returns repeatedly without any output. This causes
high cpu load.
I also confirmed that the following patch for xwin-xdg-menu
resolves the issue.
--- execute.c.orig 2017-03-22 05:31:53.000000000 +0900
+++ execute.c 2021-06-22 10:47:28.917675400 +0900
@@ -100,30 +100,38 @@
default: /* parent */
{
+ int stdout_ok = TRUE, stderr_ok = TRUE;
close(stdout_filedes[1]);
close(stderr_filedes[1]);
printf("executing '%s', pid %d\n", (char *) cmd, pid);
/* read from pipes, write to log, until both are closed */
- while (TRUE) {
+ while (stdout_ok || stderr_ok) {
fd_set readfds, errorfds;
- int nfds = max(stdout_filedes[0], stderr_filedes[0]) + 1;
+ int nfds = 0;
FD_ZERO(&readfds);
- FD_SET(stdout_filedes[0], &readfds);
- FD_SET(stderr_filedes[0], &readfds);
+ if (stdout_ok) {
+ FD_SET(stdout_filedes[0], &readfds);
+ nfds = max(nfds, stdout_filedes[0] + 1);
+ }
+ if (stderr_ok) {
+ FD_SET(stderr_filedes[0], &readfds);
+ nfds = max(nfds, stderr_filedes[0] + 1);
+ }
errorfds = readfds;
if (select(nfds, &readfds, NULL, &errorfds, NULL) > 0) {
- if (FD_ISSET(stdout_filedes[0], &readfds))
+ if (FD_ISSET(stdout_filedes[0], &errorfds))
+ stdout_ok = FALSE;
+ else if (FD_ISSET(stdout_filedes[0], &readfds))
LogLineFromFd(stdout_filedes[0], "stdout", pid);
- if (FD_ISSET(stderr_filedes[0], &readfds))
- LogLineFromFd(stderr_filedes[0], "stderr", pid);
- if (FD_ISSET(stdout_filedes[0], &errorfds) &&
- FD_ISSET(stderr_filedes[0], &errorfds))
- break;
+ if (FD_ISSET(stderr_filedes[0], &errorfds))
+ stderr_ok = FALSE;
+ else if (FD_ISSET(stderr_filedes[0], &readfds))
+ LogLineFromFd(stderr_filedes[0], "stderr", pid);
}
else {
break;
Jon, could you please have a look?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-06-23 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 5:49 Viet-Duc Le
2021-06-23 3:08 ` Takashi Yano [this message]
2021-06-23 16:41 ` Jon Turney
2021-06-25 0:08 ` Viet-Duc Le
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=20210623120858.83e471aa7ddbc20cd41efb2c@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
--cc=vdle@protonmail.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).