Privacy Browser Android

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.

Yup strange issue, as this started occurring when after migrating from 13 to 14.

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.

That could be a possibility too. Maybe site isolation itself ? Btw I can't reproduce this either. The crash seems to be random, only on heavier websites.

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.

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.

Site isolation is crucial to me anyways. I'd rather have the bug instead of disabling it.

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.

That's true. But I did like the Webview DevTools flags concept & it not only isolates PB, but the rest of the apps that wrap weblinks around them that didn't follow it.

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.

This behavior seems to have changed a bit on Android 15, security patch 2025-04-05. It doesn't produce a crash as much as it just reloads the app (out of memory error).

I think I might be able to resolve the behavior by storing the new intent in the saved state bundle and then processing it on restart.