-
Notifications
You must be signed in to change notification settings - Fork 325
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
Background jobs: Occasional hang #166
Comments
getting the same error, here is my logcat - have you been able to find a solution for the problem?
|
Still happening for me -- unfortunately I don't immediately notice it happening, only later when I spot the Termux notification with lingering tasks. I'm not sure this is limited to termux-notification, as I've caught other processes in similarly stuck states when launched from a background job:
The latter traces remain stuck after about 10 minutes, though the processes have likely been running in the order of hours -- these processes eventually drop off, not sure if they eventually become unwedged or they're being reaped by the system. |
Problem description
I have a number of scripts set to run via daily or twice-daily scheduled jobs, and at the end they send a notification if they've done any work. Sometimes this final notification step hangs (with the task remaining running until I manually go and kill it).
Steps to reproduce
This isn't consistently reproducible (happens maybe once a week/fortnight), but may be down to two scripts trying to send notifications simultaneously? I've tried the likes of
termux-notification -c A & termux-notification -c B
but can't immediately reproduce it.They each end with something like:
Additional information
I'll try and grab a logcat next time it happens.
The text was updated successfully, but these errors were encountered: