zellij: zellij start up extremely slow on WSL2 opensuse tumbleweed (since v0.41.1)

Basic information

I downloaded the zellij from github release, version 0.41.1 x86-64 arch.

stty size: 64 254

uname -av or ver(Windows): WSL2 opensuse tumbleweed

Issue description

Start zellij is extremly slow on WSL2 Opensuse tumbleweed.

This only happens since v0.41.1. Previously I am using v0.40.1 with no issues, it instantly starts up.

When launch zellij, the start screen hangs on this:

Loading Zellij
done

And I need to wait more than 10 seconds until zellij really starts up.

Note that this long startup time issue happened only occasionally (the chance is like about 50% or 33% for each time I tried to launch zellij)

Minimal reproduction

No configuration is needed, just use the default configuration (put a blank file as ~/.config/zellij/config.kdl) and one can observe such problem.

Other relevant information

There are no log shown in the runtime directory ($XDG_RUNTIME_DIR), just the file socket. As there are nothing error happened, just extremely long startup speed.

I am using opensuse tumbleweed on WSL2, the distribution version is 20241103-0

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 2
  • Comments: 27 (12 by maintainers)

Most upvoted comments

Amazing - I just merged the fix: https://github.com/zellij-org/zellij/pull/3767

Hope to release a patch version with this and other fixes soon. Thanks for the help troubleshooting!

Hey @rnbguy - thanks for the super fast turnaround. I pushed some more logs and a potential fix to the branch. Want to check it out and see if it still happens to you? Either way, if you could attach the logs that would be great.

It looks like the latest commit resolved the issue! I don’t see it anymore 👌 🙌

I am still sharing the log file - as it contains the other panic that I was referring to when I quit zellij: zellij.log

Again, many thanks for the quick work ! 🙏

Thanks @rnbguy ! This narrows it down quite a bit. I hope you don’t mind a few more rounds of back-and-forth? I added some log lines to help find the issue. Could you try pulling the latest changes in the branch and testing again?

He @rnbguy - I just created a debug branch with some more log statements to help us narrow down the problem. Could you compile and run debug-slow-start (happy to lend a hand or answer questions doing this), reproduce the problem and paste the logs here? Would be easiest if you clear the logs before each attempt so that things won’t get messed up.