View Single Post
Old 05-23-2021, 03:33 PM   #4
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by pbrouty View Post
Thank you. Attached is the log file.
Thanks for the logs. You're the first crashlog reporter on android (The feature was added yesterday)


Sadly this isn't a "normal" ANR and I don't see anything relevant on logs.

The message
Code:
05-23 20:52:18.852 15569 15574 I reader.launche: Thread[2,tid=15574,WaitingInMainSignalCatcherLoop,Thread*=0xeb908000,peer=0x17140190,"Signal Catcher"]: reacting to signal 3
Is the VM reacting to SIGQUIT (which happens when you press "close" on the ANR dialog) but there's no reason there that could explain why android thinks the app is not responding.

I did notice there are a few seconds between the app is paused and the framework label it as not responding. That suggests an issue in ON_STOP. In that case reverting https://github.com/koreader/koreader/pull/7630 could work.
pazos is offline   Reply With Quote