-
Notifications
You must be signed in to change notification settings - Fork 13
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
[bug] zombie process #35
Comments
Hello @tsankuanglee I need to take a look into that. So here is what I think happens before actually checking it. There is a thread that will run every x amount of time (depending your settings) to update the currency. And I think this is what is causing it to linger. Can you try setting the currency refresh time to the lowest possible (or off) and try this again and tell me this if the problem is still there. Cheers |
@tchar Thanks for the response. The lowest interval provided from the UI is None, and then one day. I changed the code to add 10 seconds as an option and tested it. Still the same results (lingering processes). This time, I tested with i3 in X11. |
Hello @tsankuanglee I have been trying to identify the issue. On my computer (Ubuntu LTS) I don't have a running ulauncher process. Here is an example from my system:
The above output is due to grep only. |
@tsankuanglee Here is the equivalent logs after using the command You can see at the timestamp Then I do
Would you mind providing the equivalent logs in your case too, so I can take a look at it? Maybe it has to do with the specific setup you have and I might have to install it to check what's going on. |
Good call, @tchar! Here you go. I waited for two more minutes so that thread keeps writing log two more times.
FYI, I did not get any API keys for any service. Thanks again for this! |
@tsankuanglee Thanks for this. I am seeing some errors, which are not normal, can you point me down to which timestamp you hit It looks like everything happens really fast (in 3 seconds). If you check my logs I wait a bit after hitting it so there are a few seconds of waiting. Can you do the same so I can see the logs until the normal startup and then wait a few seconds and then press Also, provide me if you can the settings you use on the extension. Thank you. |
I'm pasting two logs. This is the log from ulauncher's console (
This is the extension's runtime log (notice the thread lived on and created an error per minute, until I manually killed it):
|
Issue has been marked as stale due to no activity |
Is this still affecting you? |
Describe the bug
When Ulauncher exits, all other extensions exit as expected, but calculate-anything lingers. If I start another Ulauncher, there will be two calculate-anything instances running. If I exit Ulauncher again, two calculate-anything instances are lingering.
To Reproduce
Same result with these alternatives:
GDK_BACKEND=wayland
.exec GDK_BACKEND=wayland ulauncher --hide-window
in sway config and exit from widget menuExpected behavior
com.github.tchar.ulauncher-albert-calculate-anything/main.py
should terminate like other extensions.Desktop (please complete the following information)
The text was updated successfully, but these errors were encountered: