this message appears all the time in chrome developer tool's console:
Port error: Could not establish connection. Receiving end does not exist. miscellaneous_bindings:232
chromeHidden.Port.dispatchOnDisconnect miscellaneous_bindings:232
Error in event handler for 'undefined': Cannot read property 'instanceId' of undefined TypeError: Cannot read property 'instanceId' of undefined
at [object Object].<anonymous> (chrome-extension://mgijmajocgfcbeboacabfgobmjgjcoja/content_js_min.js:2:372)
at chrome-extension://mgijmajocgfcbeboacabfgobmjgjcoja/content_js_min.js:1:182
at miscellaneous_bindings:276:11
at [object Object].dispatch (event_bindings:203:41)
at Object.<anonymous> (miscellaneous_bindings:235:27) event_bindings:207
chrome.Event.dispatch event_bindings:207
chromeHidden.Port.dispatchOnDisconnect miscellaneous_bindings:235
is this a bug in chrome or there is something wrong in my chrome installation?
The security lapse involves a collection of back-end libraries called Mojo, which are used by Chromium-based browsers, including Opera, Brave and Microsoft Edge. The zero-day vulnerability is classified as high severity and has been labeled CVE-2022-307.
However, Google does confirm that CVE-2022-2856 was reported by hackers from within the Google Threat Analysis Group, Ashley Shen and Christian Resell, on July 19. It is, the advisory states, an "insufficient validation of untrusted input in Intents."
Fifth zero-day patched in 2022 The current Chrome update addresses the fifth zero-day vulnerability in Google Chrome this year that is actively exploited by threat actors: The previous four were: CVE-2022-2294 – July 4.
If you're seeing some of these problems with Chrome, you might have unwanted software or malware installed on your computer: Pop-up ads and new tabs that won't go away. Your Chrome homepage or search engine keeps changing without your permission. Unwanted Chrome extensions or toolbars keep coming back.
Today, web applications can provide these features, eliminating the need for Chrome Apps. Although the blog post above says that existing Chrome Apps will continue to be supported into the future, Google has since reversed this decision, deciding to end Chrome Apps support in June 2022.
It seems to be a problem with the Google Dictionary (by Google)
This script doesn't seem to exist or is not accessible by that port.
Based on some googling, this is a problem with a chrome extension, but it may not be clear which. (For me, it was Feedly).
The quickest way to find out which is causing the problem:
I know this could be a pain if there are a lot of extensions :/ personally, I took it as a chance to prune the unused / unworthy extensions while I was going through them.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With