-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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]: Termux terminates after ~ 4to5 Hours on Android 9 #3106
Comments
Check Maybe android runs out of memory, is the cronjob you are running slowly eating up available memory? Should be easy to check with for example htop |
-------- beginning of events 11-20 11:12:27.555 I/am_on_create_called(21961): [0,com.termux.app.TermuxActivity,performCreate] |
Run |
adb shell dumpsys activity exit-info com.termux adb: no devices/emulators found (probably syntax typo ?-) ) |
https://developer.android.com/studio/command-line/adb Connect to your phone first. |
Okay, thank you for you advice - will try to install android sdk on my Ubuntu 20.04 and then go further with this topic.
Next I'll try to Connect Device via USB and USB Debugging on : Takes some times, will get back here |
adb shell dumpsys activity exit-info com.termux Unknown command: exit-info (exit.info com.termux) did not work ?-) adb shell dumpsys activity |
That commands must have been added after android 9. But your termux has been running even after
To find exact reason, you can instead turn on wireless debugging and run A more general command could be Anyways, this is not something termux itself can fix, since termux is getting killed even with a foreground service. |
Thank you - I will turn on Wireless Debugging and do so... Seems that Android 9 does not offer the wireless debugging feature - i did not find ist in the developer settings. I'll try your command anyway... |
Welcome. |
adb logcat | grep -E "(ActivityManager: Killing )|(libprocessgroup: Successfully killed)" > kills.txt |
https://developer.android.com/studio/command-line/adb#wireless
Does not list |
adb.txt Termination / Kill happend at ~ 18:40 |
I don't see any relevant information that points on kill of Termux app. According to the log, it crashed (sigabrt):
However bug apparently in the OS, specifically UI rendering part... |
You must be the guy who emailed to our contact email. Sorry, didn't get time to look into it. Try to find when exactly does this crash happen and what's running. You could try reducing what you normally run, like don't run tmux or don't run anything and see if crash happens. Also enable verbose log level and terminal view key logging in termux settings and it should log entries before the crash happens to give you a clue. Also revert back to default fonts since you have changed those. |
Hi Thanks for your advice. I have 4 Apps installed myself that run in Background.
It is predictable that Termux that I run in Foreground as visible App terminates after 4 to 5 Hours. While Wireguard, Anydesk, Discreet Launcher still kept alive and running. (PS: I could live with a workaround that would stops and starts Termux after 3 hours via Reboot or Restart, but I don't know how to enable this Workaround while I am not rooted. Tablet reboots once a Day between 23:57 and 23:59 via Android Reboot plan... ) |
Issue is very unlikely to be other apps, issue is likely whatever you are running inside termux terminal or possibly the os. |
Currently I think about to run top or htop periodically in batch mode and dump results into log.txt until termux terminates. The last minutes before termination would be interesting in focus of the running processes inside termux that might cause this behaviour... (* In the meantime, found an app that schedules restart of termux and brings it into foreground: every 5 minutes [Open App Scheduler] ) |
Problem description
Launching Termux 0.118.0, lauching sshd and crond via Termux-Boot, doing some work via crond every 5 min and monitor/visualize results of work in 9 to 10 tmux panes. Wake-Lock is held. Battery optimisazion is disabled. Wireguard VPN active. Not Rooted.
Steps to reproduce the behavior.
Start Termux on Android 9. Wait 4 to 5 Hours. After that Time Termux dies or gets terminated.
What is the expected behavior?
Run 24/7
System information
The text was updated successfully, but these errors were encountered: