Bug #1285
closedCrash on 3.19.3
0%
Description
Hello,
my smartphone (Xiaomi POCO F5 - HyperOS 2 - Android 15) reported 2 crash on Privacy Browser 3.19.3 installed from the F-Droid. It crashes when it's in background (or when I put it in background?) but in the normal usage it works fine.
Unfortunately I have no other information than the log below. The "12 more" and "14 more" are not clickable so this is everything I get from the report. I hope it could be useful anyway
java.lang.IllegalStateException: Could not execute method for android:onClick
at g.F.onClick(Unknown Source:150)
at android.view.View.performClick(View.java:8215)
at android.view.View.performClickInternal(View.java:8192)
at android.view.View.-$$Nest$mperformClickInternal(Unknown Source:0)
at android.view.View$PerformClick.run(View.java:32681)
at android.os.Handler.handleCallback(Handler.java:959)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loopOnce(Looper.java:249)
at android.os.Looper.loop(Looper.java:337)
at android.app.ActivityThread.main(ActivityThread.java:9638)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:615)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at g.F.onClick(Unknown Source:138)
... 12 more
Caused by: java.lang.NullPointerException: null cannot be cast to non-null type android.widget.FrameLayout
at com.stoutner.privacybrowser.activities.MainWebViewActivity.closeTab(Unknown Source:148)
... 14 more
Updated by Soren Stoutner 8 days ago
- Status changed from New to Closed
- Assignee set to Soren Stoutner
Based on the log, it looks like your OS is killing the main FrameLayout and then trying to access it anyway. Usually this has to do with over aggressive power management features. For reasons that don't make sense to me, most ROMs try to play with these settings because they think they can do better than the Android defaults. However, usually all they end up doing is creating bugs that cause apps to crash.
There probably isn't much I can do about this unless it is a problem that can be replicated in standard AOSP Android. However, you might find some inspiration on how you can fix this behavior on your device by looking at the following:
Updated by F. G. 8 days ago
Soren Stoutner wrote in #note-1:
Based on the log, it looks like your OS is killing the main FrameLayout and then trying to access it anyway. Usually this has to do with over aggressive power management features. For reasons that don't make sense to me, most ROMs try to play with these settings because they think they can do better than the Android defaults. However, usually all they end up doing is creating bugs that cause apps to crash.
There probably isn't much I can do about this unless it is a problem that can be replicated in standard AOSP Android. However, you might find some inspiration on how you can fix this behavior on your device by looking at the following:
Thank you very much. Xiaomi always kill apps by its own... Thanks for checking, sorry for the useless report :-)
Updated by Soren Stoutner 8 days ago
That's fine. It is good to have this bug report because others can search for the error message and find the link to https://dontkillmyapp.com, which might be helpful to them.