Alacritty causing 1-2 mins of busy cursor on i3 desktop, and extreme i3 performance issues

[RonanZer0]

Which operating system does the issue occur on?
Arch Linux

If on linux, are you using X11 or Wayland?
X11

Version: current version in arch user repository, unsure how to check version number

Opening an Alacritty instance causes the mouse to be stuck on "busy" instead of the normal cursor, only when the mouse is hovering over the i3wm desktop. Not the biggest of deals, but can be distracting. This effect seems to usually go away after approximately 1.5-2 to minutes, but it persists even after the terminal is closed. Running i3 restart resets the cursor to normal.

Alacritty also seems to cause performance issues specifically with i3 after long periods of time and many terminals opened and closed. The longer my session lasts and the more Alacritty terminals I open (and close), the worse i3 performance gets (e.g. switching between workspaces becomes extremely slow) while application performance is fine. It eventually becomes unusuable. These issues only happen when I'm using Alacritty.

[cideM]

Are you sure that's because of alacritty? I can reproduce the issue but then again I have the busy cursor super often in i3

[DuBistKomisch]

https://wiki.archlinux.org/index.php/I3#Mouse_cursor_remains_in_waiting_mode

[jwilm]

Closing this. I haven't experienced anything like this myself, and it sounds like it's unlikely due to Alacritty. Feel free to reopen if there is evidence otherwise.

[AndrewVos]

This is actually due to alacritty not sending some sort of "ready" signal or whatever.

https://faq.i3wm.org/question/118/mouse-cursor-remains-waiting-after-closing-last-tile.1.html

A workaround is to do something like:

bindsym $mod+Return split h; exec --no-startup-id alacritty

That will get rid of the busy pointer.

--no-startup-id is the important part.

[eyadsibai]

I am experiencing the same thing with alacritty. I understand that adding --no-startup-id is a workaround, but would be nice to have a solution

[DiggsAsura]

I experience the same thing on i3, xorg, debian 11