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

:spawn -d processes are reported as "running" even when they are not #8113

Open
emanuele6 opened this issue Feb 26, 2024 · 1 comment
Open

Comments

@emanuele6
Copy link
Contributor

Version info:

qutebrowser v3.1.0
Git commit: 
Backend: QtWebEngine 6.6.2, based on Chromium 112.0.5615.213 (from api)
Qt: 6.6.2

Does the bug happen if you start with --temp-basedir?:
Yes

Description
When you spawn a detached process, qutebrowser shows it as pid 0, and says it is running even though it is not.

completion qute://process/
file file

Since detached processes are not qutebrowser's children, it makes sense that it cannot know their exit status, and that it does not get notified when they terminate, but it would be less confusing if qutebrowser didn't say that their status is "running".

How to reproduce
:spawn -d echo hi

@emanuele6
Copy link
Contributor Author

There could be a special detached status, but maybe detached processes should just not be shown at all in :process completion; qutebrowser cannot provide any useful information about them except their commandline (and maybe potentially their pid).

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