Could CheckNlog crash?
Short answer: yes.
After many tests I have to admit that, unfortunately, and despite all the improvements, it is.
To get some data that the application shows it is needed to use the reduced version of busybox included and some calls to Linux executables. After consulting lots of documentation, the problem is to call external executables from java -Android- always carries a risk that the executable process remains unconnected from java application that started it, causing an error in the application and leaving the process orphan, difficult to locate and terminable only by a root user. A reboot of the device is the easy solution.
The worst of these failures is that they are almost random and all documentation is about methods to mitigate it only, no way to avoid them, great ...
In my defense I must say that due to the nature of these failures, I checked as several other reputable applications also suffer from these errors that leave orphan and forgotten processes in the list of active processes causing application crash. Sometimes these applications and mine can be started again and work properly again but the initial process or processes continue orphans and lost in the list of active processes.
I noticed that when CheckNlog was not successful, other applications have given error just before or after it.
This may be due to some process that is overloading the system or a bad system startup.
Nothing strange, almost everyone has seen after a device reboot certain applications that should, not be initiated or certain parameters were not applied.
The advertisements displayed on the free version should not cause the error, however the Pro version without ads seems more stable.
Anyway these errors are very casual but some devices, roms or configurations may be more prone to them.
Please give a try to CheckNlog at:
https://play.google.com/store/apps/details?id=com.marvalmel.checknlog
