Can you be more specific about which devices you've observed the problematic behaviour on? We have never seen this ever, so we would need some way to reproduce it. Even just one specific device/OS version/application combination where this happens would be a good start.

>>>Can you be more specific about which devices you've observed the problematic behavior on?
 the issue was observed on Samsung Tab S2 (sm-T815) running Android 6.0.1 with Webview 51.xx.

Steps to recreate this issue :
 1) In Google Play Store App--->settings, ensure that automatic updates is enabled and ensure the tablet has internet connection.
 2) Now navigate to Android Settings-->Apps-->Android System Webview and uninstall if any earlier installed updates.
 3) And then install a webview based hybrid application (preferably an application that has some html5 based canvas and SVG animations that are active when the app is in foreground) 
 4) Start this application and leave it running in the foreground 
 5) Wait for Google Play Store to push WebView update onto the tablet and observe that immediate after installation of webview update the application in foreground hangs or does not accept any user input or does not restart.

thanks
Padua

Can you suggest a *specific* application that you have confirmed definitely has this issue, to make sure we are testing something you know is broken?

Can you use try with app
https://play.google.com/store/apps/details?id=com.medtronic.mcls_us&hl=en

Hm, doesn't look like we have a galaxy tab S2 anywhere :/

Is there another device where you've seen this?

Thank you for providing more feedback. Adding requester "torne@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

Satyavathi, do we have a Galaxy Tab S2 anywhere that I just can't see on the skylab stock list? Or could we try testing this app on a similar samsung device? (at least the same OS version)? Specifically we're looking for the app not working after a webview update - it's expected to be killed, but it should restart just fine after the update is complete.

torne@ we do have 2 Galaxy tab S2's. sbashyam@ from our team will check and update the bug soon.

Thanks!

sbashyam@ you had worked on this bug few weeks back. Could, you update your findings?

Thanks!

I see the same observation as comment #7 with 2 Samsung Tab S2(MMb29K/6.0.1)devices  with System image 49.0.2623.105 when MCL_Smart(2.1.0) is opened in foreground and upgrading by side loading 51.0.2704.117 OR Playstore update does kill the foreground app  but when relaunched , able to use the application.

your description sounds like the right behavior to me.  passing to Torne in case he wants more investigation.

OK, so we can't reproduce this with the device/app mentioned, it's not a behaviour we've had reported by anyone else, and I can't figure out how this could possibly happen, so I don't think there's anything else we can do with the information provided I'm afraid :/

Closing for now; we can reopen if you can suggest a more specific way to reproduce this issue, or provide a bugreport and system logs from this happening on a device that we can look at.