project-repo / cagebreak

Cagebreak: A Wayland Tiling Compositor Inspired by Ratpoison
MIT License
279 stars 20 forks source link

Question on starting processes #79

Closed sodface closed 5 months ago

sodface commented 5 months ago

https://github.com/project-repo/cagebreak/blob/ace4ff04c61806d9c321392cbdc443435a6274ee/keybinding.c#L1710-L1719

I've researched this but I can't figure out if what I'm seeing is user error on my part or possibly an issue, and, if an issue, where it should be reported.

I'm starting cagebreak from .profile after logging in from tty:

exec dbus-run-session -- cagebreak -e > cagebreak.log 2>&1

I have a keybinding to start lite-xl:

bind e exec lite-xl

If I login, launch lite-xl via the keybinding, and then kill cagebreak with ctrl+t shift+d (or cagebreak crashes to tty for whatever reason) the lite-xl process continues to run and consumes 100% cpu on one thread. When I start a new cagebreak session, everything is fine but that lite-xl process is still running headlessly and consuming 100% of a cpu thread.

I've seen the same thing with other applications (mpv I think) though lite-xl is the most recent and always repeatable.

Applications launched via the exec keybinding become children of init not cagebreak so it makes sense that they wouldn't exit when cagebreak exits... but still what I'm seeing doesn't seem optimal. I'm just not sure how I should address it?

sodface commented 5 months ago

I don't think this is a Cagebreak issue. I'm going to close this.

See also: https://github.com/lite-xl/lite-xl/issues/1464