Can you provide a net internals log?   Refer to instructions:  

https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Hrm....  None of those files are Chromium file names.

#1:

Is this a fork of Android? What version of Android is it?

In the meanwhile I add another detail. When I put on standby the STB I have to close my application according to the specifications of the behavior to be adopted for my app. If I close the app in a normal way (with finish the webview-activity) the bug is present, so after I power on the STB and I wait to the network I see the bug. Instead if I kill completely the app with System.exit(0) the webview starts normally. Could be a cache problem of my application?

I'll provide soon net internal logs.

I use AndroidTV Lollipop 5.1.1, I write this detail also on my first post.

Thanks to all.

Is this a device that comes with the Google Play Store preinstalled, and receives WebView updates via the Play Store? If so, can you check what version of "Android System WebView" is installed on the device, in the application list?

If it's not, then we can't do anything about this - non-Play devices don't use our webview binaries and so the vendor of the device may have made any changes/customisations they wish, and we cannot update the webview on these devices.

Android System Webview is installed on the device as system app and the version is 52.0.2743.98.

Well, then that's very confusing, because the log messages you quote refer to filenames that don't exist in WebView/chromium at all, and so I don't see how they can be coming from the current webview version.

Can you attach a *full* system log from the device for a case where this problem occurs, starting from *before* you launch the application that uses webview? This will capture the log lines printed early in startup when webview is loaded, which will confirm exactly where it's loaded from and what version it is?

Hi I attached full logs where I renamed my package name with *myapp*.
Logs started when I press power ON with remote controller to STB afterstandby (screen off mode).

Thank you

Deleted: logs_forChromium.txt 247 KB

logs_forChromium.txt 247 KB View Download

Your app was already running (as a cached background process) at the start of this log, so the relevant webview startup logs aren't present. You need to completely kill the app process (from adb shell, or by force stopping it in the UI) first.

(specifically, there should be log lines tagged with "WebViewFactory" that get printed during startup of a webview app)

If you want only the version name and code this is the log:

09-21 16:27:52.201 2797-2797/*myapp* I/WebViewFactory: Loading com.google.android.webview version 52.0.2743.98 (code 275609800)

No, I want to see the complete log from startup so that I can read the full logs in context and figure out where they're coming from, because the excerpts you've posted aren't something we can explain easily.

Here you are. These are the logs after standby of STB. My app was completely killed from Android settings before STB goes to standby mode.
After screen on I captured the logs.
Webview in this case starts normally, but if I repeated the same test with finish the activity before doing standby, I have the bug that loads slowly.

I hope I was clear now.

Deleted: logs_normal_startupWebview_after_standby 314 KB

logs_normal_startupWebview_after_standby 314 KB View Download

So two things:

1) Do I understand correctly that the latest log isn't a log from when the problem actually occurred? That's not really useful ;) What I wanted is a log that begins before your app starts, and ends after the problem has been reproduced.

2) What i can tell from the log anyway is that all the openssl errors you posted in the original post are not even coming from your application and so are irrelevant to the problem entirely. That's the TV device's cast media shell (the thing that receives casted content like a chromecast), which is a separate app that doesn't use webview at all. So, those messages don't help at all and this may not have anything to do with networking even.

Thank you for providing more feedback. Adding requester "ckrasic@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

marco...@: Could you respond to the questions in c#14?  We need more information to continue making progress on this bug.

No feedback was received in the last 30 days from reporter "marcopistons@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue.

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