wezterm-gui uses 100% CPU

[wilriker]

Describe the bug

wezterm-gui uses up 100% CPU (i.e. one CPU core) while being idle. Therefore it is very laggy accepting input as well as rendering output. Basically it's unusable this way.

Environment (please complete the following information):

• OS: ArchLinux X11 (using AUR wezterm-bin package)
• Version: wezterm 20210314-114017-04b7cedd
• The active keyboard layout name: GB

To Reproduce

I just need to launch wezterm.

Configuration

I don't have a wezterm.lua configuration file.

Expected behavior

Being a usable terminal. ;-)

[wez]

I haven't seen behavior like this before. What are you running inside the terminal?

Please run: WEZTERM_LOG=trace wezterm 2> /tmp/log.txt and let it run for ~30 seconds or so, then attach that log file to this issue. That should show us roughly what is happening inside.

[wilriker]

It simply spawns an instance of fish and then does nothing.
log.txt

[wez]

It appears as though there is a continual stream of events from your window manager about changing the selection and resizing, even though nothing is changing. Which window manager are you using?

[wilriker]

I use herbstluftwm a tiling window-manager.

[wez]

Please give https://aur.archlinux.org/packages/wezterm-git/ a try when you have a few moments to see if the commit I just pushed helps!

[wilriker]

That seems to have fixed it! Thanks for the quick solution. Now I can continue evaluating wezterm. 👍

[wilriker]

Maybe one last question: is there a way to generate a wezterm.lua to start from for customization?

[wez]

We have #548 open to add some example-driven configs to the docs. I don't think it is necessarily a great idea to have a big config with every possible thing in it, because it would be difficult to consume and difficult to maintain. Having a base config with the most likely changed options in it feels reasonable though.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.