Re comment #23: - This happened to me on both xenial and also on zesty (though it took a while to trigger on the later) => disabling media router (or clearing the profile) fixed it.
Also linking https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477 as it says: * Disable builtin media router since it only works with official Google Chrome builds, not chromium (closes: #833477).
Re comment #23:
- This happened to me on both xenial and also on zesty (though it took a while to trigger on the later)
=> disabling media router (or clearing the profile) fixed it.
Also linking https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 833477 as it says:
* Disable builtin media router since it only works with official Google
Chrome builds, not chromium (closes: #833477).