User feels like white screen without content, but when user types the text, text is getting entered but not visible. 

Hello LG, I don't think we are seeing issues like this recently.

Does this happen on only Android O? Did you see this issue with other version of WebView?

We were reported the issues like this only at the Android O.
And we found the issues at the different versions of Webview.
(64.0.3282.137, 66.0.3359.126)

Thank you.

Is that possible related to your device? Can you repro this on a Pixel or Nexus device?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Adding Needs-Feedback label from comment #5?

Thanks!!

We have no Nexus or Pixel device. So we can not share the result of what you requested.

Thanks.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Please refer to the analysis for the suspicion of this log file.

Thank you.

Deleted: blank_issue_log.txt 33.8 KB

blank_issue_log.txt 33.8 KB View Download

Hello LG, the log you attached isn't useful, that's just a false alarm. It just says you have no such Android API available on your device (API level 26) and that API is only on API level 27 and above, see crbug.com/791099 for more info.

To be more clear, this log looks like a crash, but it is harmless.

For a better understanding.

We use webview for email viewing and for composing email and editing email signatures.

 

Once you have a problem, you will not be able to see the contents of any page using webview (Composing email, Detail View ..).

After re-creating the email process (kill process and restarting), the web view will work normally.

 

i found that child connection (or child process service) is created when starting compose(view) activity or fragment.

but in issue case, there are no creaeting child connection(or child process service) logs.

 

Could this be the cause?

Deleted: capture.PNG 65.3 KB

	capture.PNG 65.3 KB View Download

Deleted: PussADB_20180510_085346_main_merged.zip 3.7 MB

PussADB_20180510_085346_main_merged.zip 3.7 MB Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

cc'ing boliu@ for better knowledge of child process.

LG, could you please provide some more information:

 1. Does this reproduce on any LG devices which have already been shipped? If so, which ones?
   a. If you have not yet shipped Android O, please use an N device and go to Developer options > Multiprocess WebView > toggle to "on"
   b. If it repros on the N device, please let us know which device that you used
 2. What is the full package name of the email app?
   a. Please provide a play store for this app if possible
   b. If this app can be installed on a non-LG phone, please indicate so

we request to check below logs are normal or not. And there are some link where they mention some rendering issues.. can you check any such reason for this issue https://developers.google.com/web/updates/2018/02/chrome-65-deprecations 

05-11 07:21:05.246  2022  4052 I ActivityManager: Start proc 2227:com.android.chrome:sandboxed_process10/u0i28 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService10
05-11 07:21:07.169  2022  2708 I ActivityManager: Killing 2227:com.android.chrome:sandboxed_process10/u0a277i28 (adj 0): isolated not needed
05-11 07:21:08.362  2022  3803 I ActivityManager: Start proc 2511:com.android.chrome:sandboxed_process11/u0i29 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService11
05-11 07:21:09.949  2022  3963 I ActivityManager: Killing 2511:com.android.chrome:sandboxed_process11/u0a277i29 (adj 0): isolated not needed
05-11 07:21:14.029  2022  3804 I ActivityManager: Start proc 2832:com.android.chrome:sandboxed_process12/u0i30 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService12
05-11 07:21:30.523  2022  2438 I ActivityManager: Killing 30559:com.android.chrome:sandboxed_process0/u0a263i25 (adj 900): remove task
05-11 07:22:10.395  2022  3871 I ActivityManager: Killing 2832:com.android.chrome:sandboxed_process12/u0a277i30 (adj 0): isolated not needed
05-11 07:22:11.554  2022  3871 I ActivityManager: Start proc 5253:com.android.chrome:sandboxed_process13/u0i31 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService13
05-11 07:22:22.165  2022  2649 I ActivityManager: Killing 5253:com.android.chrome:sandboxed_process13/u0a277i31 (adj 900): remove task
05-11 07:23:51.336  2022  2693 I ActivityManager: Start proc 8134:com.android.chrome:sandboxed_process0/u0i32 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService0
05-11 07:23:57.735  2022  2787 I ActivityManager: Killing 8134:com.android.chrome:sandboxed_process0/u0a277i32 (adj 0): isolated not needed
05-11 07:27:04.509  2022  2022 I ActivityManager: Start proc 12724:com.android.chrome/u0a212 for service com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService
05-11 07:27:04.509  2022  2022 I ActivityManager: Start proc 12724:com.android.chrome/u0a212 for service com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService
05-11 07:29:16.134  2022  3840 I ActivityManager: Start proc 16151:com.android.chrome:sandboxed_process1/u0i33 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService1
05-11 07:29:35.209  2022  2787 I ActivityManager: Killing 16151:com.android.chrome:sandboxed_process1/u0a277i33 (adj 0): isolated not needed
05-11 07:30:51.230  2022  2762 I ActivityManager: Start proc 19132:com.android.chrome:sandboxed_process2/u0i34 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService2
05-11 07:30:54.341  2022  3841 I ActivityManager: Killing 19132:com.android.chrome:sandboxed_process2/u0a277i34 (adj 0): isolated not needed
05-11 07:31:22.184  2022  4053 I ActivityManager: Start proc 20146:com.android.chrome:sandboxed_process3/u0i35 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService3
05-11 07:31:30.512  2022  2708 I ActivityManager: Killing 20146:com.android.chrome:sandboxed_process3/u0a277i35 (adj 0): isolated not needed
05-11 07:31:33.537  2022  2787 I ActivityManager: Start proc 20458:com.android.chrome:sandboxed_process4/u0i36 for webview_service com.lge.email/org.chromium.content.app.SandboxedProcessService4
05-11 07:32:50.569  2022  3961 I ActivityManager: Process com.android.chrome (pid 12724) has died: cch+6CEM 

boliu@ I assume these logs are OK (I see similar logs when I use gmail)

LG, please answer the questions in comment #17.

1. we did't test if this issue is reproducible on shipped model. (but this issue is reported many times in O-OS model on developing device)
   we don't know how to reproduce this issue exactly so.. we are trying in many ways on G5 N OS model with multi-process webview options.
2. "com.lge.email" is full package name of LGEmail.
3. we don't support play store. so we are checking to share APK but, we need to get confirm to share it.
   we have dependency on LG framework, and OS, so.. even if we share the APK, you need LG O OS device..(like.. V30 upgraded to O-OS or other O-OS LG device....)

If the APK only runs on LG devices, this is nearly impossible for us to debug. Please provide a minimal repro APK, which is compatible with Nexus devices. Please include a zip of the source code as well as the compiled APK.

We checked to share apk but it is not allowed sharing.
Instead, we can share log using modified chrome apk with log added if you want.
or...could you check try to reporduce it with O-OS upgrade LG Device (v30..)

> We checked to share apk but it is not allowed sharing.

I'm sorry, but our team cannot debug this unless your engineers provide a minimal repro APK. We have the same requirement for all application authors. Therefore, I'm closing this as non-reproducible.

I understand LG has valid privacy concerns. Unfortunately, you'll need to find a solution on your own, as this is not a known issue in either WebView or Chrome.

re #19

> boliu@ I assume these logs are OK (I see similar logs when I use gmail)

Yeah that's fine. It's showing creating and destroying the renderer process in webview. Renderer process is created when the first webview is created, and destroyed when the last webview goes away. So in this case, I guess you were probably opening in emails or something, ie quickly switching between creating and destroying webviews.

Yup, that's how I repro'd the logs.

If LG can provide a repro application, please let us know so we can continue investigation.