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

Wev crashes "Error marshalling request: Too many open files" #4878

Closed
2 tasks done
bendi-github opened this issue Jun 12, 2024 · 6 comments
Closed
2 tasks done

Wev crashes "Error marshalling request: Too many open files" #4878

bendi-github opened this issue Jun 12, 2024 · 6 comments

Comments

@bendi-github
Copy link

bendi-github commented Jun 12, 2024

Issue description

When running wev to debug input events, the log gets filled up with

[09:     xdg_surface] configure: serial: 32353
[10:    xdg_toplevel] configure: width: 848; height: 330
                      activated tiled-left tiled-right tiled-top tiled-bottom

and eventually crashes

error marshalling arguments for create_pool: dup failed: Too many open files
Error marshalling request: Too many open files

Input events are still logged while the log is being spammed.

Version

0.23.0b3.dev350+g6ee02e5c

Backend

Wayland (experimental)

Config

Default, I just changed the modkey to `mod1` for testing

Logs

Nothing shows up, besides the usual warnings the default config throws on wayland

Required

  • I have searched past issues to see if this bug has already been reported, and it hasn't been.
  • I understand that people give their precious time for free, and thus I've done my very best to make this problem as easy as possible to investigate.
@jwijenbergh
Copy link
Contributor

0.23.0b3.dev350+g6ee02e5c

that is a really old version, please test on the latest

@bendi-github
Copy link
Author

git clone https://github.com/qtile/qtile.git
cd qtile
pip install .
pip install --config-setting backend=wayland . 

qtile-0.26.1.dev25+g29695c71

The issue persists. I tested a nested qtile instance in additon to starting it directly via sddm. I noticed when I launched wev in a nested session, it crashed faster when compared to a non-nested session.

@tych0
Copy link
Member

tych0 commented Jun 15, 2024

I wonder if this is really a dupe of #4821, that we're leaking stuff when certain events happen, and in the wev model these things end up as file descriptors?

@jwijenbergh
Copy link
Contributor

#4880 fixes this for me

@jwijenbergh
Copy link
Contributor

I wonder if this is really a dupe of #4821, that we're leaking stuff when certain events happen, and in the wev model these things end up as file descriptors?

I doubt it, this seems like a recent regression in git

@jwijenbergh
Copy link
Contributor

Fixed in git

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

No branches or pull requests

3 participants