Bug #1106
openNew intents sometimes aren't loaded on restart on Android 14 (WebView crash)
0%
Description
When restarting from a new intent, sometimes the old tabs are restored but the new URL isn't loaded.
Files
Updated by Soren Stoutner 11 months ago
- File Privacy Browser Android 3.15.1 Logcat.txt Privacy Browser Android 3.15.1 Logcat.txt added
- Status changed from New to In Progress
- Priority changed from Next Release to 3.x
So, it turns out that this bug is actually caused because Chromium is crashing on restart.
[10-27 22:19:01.173 2343: 2343 E/chromium ]
[ERROR:aw_browser_terminator.cc(112)] Render process (14421) kill (OOM or update) wasn't handed by all associated webviews, killing application.
This causes the new intent to be lost and the app to be restored with the previous tabs.
There probably isn't anything I can do about it, but it will likely be fixed by a WebView update.
Updated by Soren Stoutner 11 months ago
- Subject changed from New intents sometimes aren't loaded on restart on Android 14 to New intents sometimes aren't loaded on restart on Android 14 (WebView crash)
Updated by Soren Stoutner 9 months ago
Here is a fuller crash log:
[ 01-03 11:13:20.916 9026: 9060 W/cr_ChildProcessConn ] onServiceDisconnected (crash or killed by oom): pid=17624 bindings:W [ 01-03 11:13:20.940 9026: 9060 W/cr_ChildProcessConn ] onServiceDisconnected (crash or killed by oom): pid=14346 bindings:W S [ 01-03 11:13:20.943 9026: 9060 W/cr_ChildProcessConn ] onServiceDisconnected (crash or killed by oom): pid=9188 bindings:W S [ 01-03 11:13:20.954 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(154)] Renderer process (17624) crash detected (code -1). [ 01-03 11:13:20.957 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(154)] Renderer process (9627) crash detected (code -1). [ 01-03 11:13:20.960 9026: 9060 W/cr_ChildProcessConn ] onServiceDisconnected (crash or killed by oom): pid=18692 bindings:W S [ 01-03 11:13:20.966 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(154)] Renderer process (9070) crash detected (code -1). [ 01-03 11:13:20.971 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(154)] Renderer process (9188) crash detected (code -1). [ 01-03 11:13:20.971 9026: 9060 W/cr_ChildProcessConn ] onServiceDisconnected (crash or killed by oom): pid=9627 bindings:W S [ 01-03 11:13:20.980 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(154)] Renderer process (14346) crash detected (code -1). [ 01-03 11:13:20.984 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(154)] Renderer process (18692) crash detected (code -1). [ 01-03 11:13:20.994 9026: 9026 E/chromium ] [ERROR:aw_browser_terminator.cc(110)] Render process (9627) kill (OOM or update) wasn't handed by all associated webviews, killing application.
Updated by Soren Stoutner 9 months ago
Currently I am investigating if making changes to WebView DevTools is responsible. It appears to be so, but I do want to do a bit more testing to narrow down which one.
Updated by Soren Stoutner 8 months ago
In my testing, disabling the WebView DevTools settings that relate to site isolation and partitioning result in this problem happening less frequently, but it doesn't eliminate it. In other words, the root of the problem is something else, but site isolation and partitioning aggravates whatever it is.
I have updated the text at https://www.stoutner.com/webview-devtools/ with a warning.
Updated by Soren Stoutner 8 months ago
On my Pixel 5, WebView 121.0.6167.143 fixes this issue, but only if all the site isolation options in WebView DevTools are disabled.
I would assume that a future WebView update will fully resolve the problem.
Updated by Soren Stoutner 8 months ago
As I have already explained in other places, Privacy Browser already does most of what other browsers call site isolation all the time anyways. Enabling the site isolation options in WebView DevTools adds a little, tiny bit of additional protection. but only if your device has already been fully compromised by malicious JavaScript.
Updated by Soren Stoutner 8 months ago
That is a good point. Enabling site isolation in WebView DevTools does protect other apps besides Privacy Browser.
Of course, it also means this bug affects all other apps that use WebView. On my Pixel 5, with site isolation enabled and this current bug, it makes a lot of apps on my device crash frequently.