error in chrome dev tools - Unchecked runtime.lastError: The message port closed before a response was received.
See original GitHub issueAn error appears in the console in chrome dev tools upon launching Live Server
Unchecked runtime.lastError: The message port closed before a response was received.
- browser - Chrome (desktop) version 72
- Live Server: 1.30.2
- Platform: Windows
- Visual Studio Code: latest
Issue Analytics
- State:
- Created 5 years ago
- Comments:41 (1 by maintainers)
Top Results From Across the Web
How to fix 'Unchecked runtime.lastError: The message port ...
The issue is most likely a mishandled async response to runtime.sendMessage. As MDN says: To send an asynchronous response, there are two ...
Read more >"The message port closed before a response was received ...
error in chrome dev tools - Unchecked runtime.lastError: The message port closed before a response was received.
Read more >Unchecked runtime.lastError: The message ... - Google Support
This message appears frequently in my console. From Google searches, I gather that the likely cause is an extension which uses chrome.runtime.
Read more >Error Unchecked runtime lastError The message port closed ...
I'm using Laravel . This issue started to show lately and it shows even in the old git branches. This error only shows...
Read more >Unchecked runtime.lastError: The message ... - Google Groups
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group. To unsubscribe from this group and stop receiving...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi vk011 - This might be an issue with an extension you have from chrome. Try disabling them (chrome://extensions) and enabling them one by one to find the culprit. This worked for me.
https://chrome.google.com/webstore/detail/meddlemonkey/moihledlmchhofenpacbhphnbnpakgmo