Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alt shortcuts sometimes letting through key presses #3885

Open
Garmelon opened this issue Dec 20, 2024 · 0 comments
Open

Alt shortcuts sometimes letting through key presses #3885

Garmelon opened this issue Dec 20, 2024 · 0 comments

Comments

@Garmelon
Copy link

Garmelon commented Dec 20, 2024

Issue description

When a CPU-intensive application runs, alt-based keyboard shortcuts are sometimes let through to the programs running in the panes instead of being captured by zellij.

So far, I've observed key press leakage with the shortcuts alt+h, alt+l, alt+[], alt+f. I could not observe leaks with any ctrl-based shortcuts.

Minimal reproduction

Steps 1 to 4 can probably replaced by any other way to get 100% CPU usage on all cores. The program generating the CPU load does not need to run in zellij.

  1. Clone https://github.com/Garmelon/blamegraph
  2. Clone a big repo (e.g. https://github.com/NixOS/nix)
  3. In the blamegraph repo, run cargo run --release -- /tmp/bgdata gather path/to/nix
  4. Wait until the progress bars appear (may take a minute or two)
  5. Open a new zellij session
  6. Try various alt-based keyboard shortcuts, eg. switching between panes
  7. Observe that sometimes, the key presses are handled by zellij and sometimes they are handled by the underlying program running in the focused pane

Blamegraph will, after an initial period of analyzing the git repo, call git blame in parallel on all cores, which usually takes close to 100% of each core.

Other relevant information

System info: Arch linux, Gnome (Wayland), Gnome terminal, zellij 0.41.2

For bonus points, run cargo run --release -- /tmp/bgdata graph-years years.html after you've reproduced the bug :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant