From: Fujii Hironori <fujii.hironori@gmail.com>
To: jsberg-bnl@outlook.com, 61258@debbugs.gnu.org
Subject: bug#61258: 29.0.60; pgtk build from git, WSLg, slow, heavy cpu use
Date: Wed, 2 Aug 2023 07:01:27 +0900 [thread overview]
Message-ID: <CALus1PnKLEtHwDHu6t+Za4e0iGO7JKOCgmGD5DBuHtVBR0htiQ@mail.gmail.com> (raw)
In-Reply-To: <PH8PR14MB6016E602FE2BE968DFDB8D4E9AD79@PH8PR14MB6016.namprd14.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
> Emacs built with pgtk. Editing in f90 mode, though I don't think this is
> important. Display is WSLg. Severe input lag, to the point off becoming
> unusable, gets worse with more frames (or just time?). Heavy CPU usage by
> emacs while doing anything. Problem not seen when not built with pgtk.
I'm observing a similar high CPU usage problem with Emacs 29.1 on WSL1 and
X server, not with WSLg.
As suggested by
https://www.reddit.com/r/emacs/comments/urivlg/high_cpu_usage_in_wsl_with_emacs_29050/
reverting
https://github.com/emacs-mirror/emacs/commit/fa52782f5c4eaef7138534766dfc8a29465785b2
solves the problem for me.
[-- Attachment #2: Type: text/html, Size: 893 bytes --]
next prev parent reply other threads:[~2023-08-01 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:47 bug#61258: 29.0.60; pgtk build from git, WSLg, slow, heavy cpu use J. Scott Berg
2023-02-04 0:48 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 11:51 ` J. Scott Berg
2023-02-04 8:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-01 22:01 ` Fujii Hironori [this message]
2023-08-02 0:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-02 11:49 ` Eli Zaretskii
2023-08-02 13:00 ` J. Scott Berg
2023-08-03 1:00 ` Fujii Hironori
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALus1PnKLEtHwDHu6t+Za4e0iGO7JKOCgmGD5DBuHtVBR0htiQ@mail.gmail.com \
--to=fujii.hironori@gmail.com \
--cc=61258@debbugs.gnu.org \
--cc=jsberg-bnl@outlook.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).