Status Update
No update yet.
Comments
pe...@chromium.org
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ph...@chromium.org
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
is...@google.com
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
Description
Steps to reproduce the problem:
1. Install any Manifest V3 unpacked extension which uses Native Messaging Host
2. Native Messaging Host (read as "Host" further) instance will be run by the Service Worker code
3. Wait some time, possible minimize browser to background
What is the expected behavior?
After extension refresh (or Service Worker) only new Host instance should be running, old (previous) Host instance should be terminated.
What went wrong?
Case 1: After some idle time once the browser is activated the Service Worker restarted and therefore new Host instance created, but old Host instance kept running!
Case 2: Each time extension refreshed from the Extensions page (for debugging purposes) it leads to the same result as Case 1 - old Host instance kept running.
Once old Host instance tries to send anything back to the extension (let's say any external event) using the STDOUT (it's Pipe in fact) then the browser crashes completely.
Did this work before? No
Does this work in other browsers? Yes
Chrome version: 80.0.3985.0 Channel: dev
OS Version: 10.0
Flash Version: