[Bug] Chrome Extension: Unchecked runtime.lastError: The message port closed before a response was received.
See original GitHub issueBug Report
Bug Description
Viewing any website/page causes an error in the console:
Unchecked runtime.lastError: The message port closed before a response was received.
Website Address
Any website.
Steps To Reproduce
- open any website
- open the dev tools > console
- an error is written to the console (see above)
- refresh the page; error is repeated
Expected Behavior
No errors are thrown or written to the console.
Actual Behavior
Error is written out to the console.
Screenshots
n/a
System Information
- OS: Windows 10 x64
- Windows Version: 20H2
- Windows Build: 19042.1237
- Windows Feature Experience Pack 120.2212.3530.0
- Browser: Chrome Version 94.0.4606.54 (Official Build) (64-bit)
- Dark Reader Version: 4.9.37
Additional Context
Toggled all my extensions off until I found the extension throwing the above error. Disabling Dark Reader and the error is no longer thrown. Enabling Dark Reader and the error is shown again.
Possible Resolution?
- Stackoverflow: https://stackoverflow.com/a/56483156/9664
- Be sure to read the comments of the linked answer as well; accepted answer is crap.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:13 (5 by maintainers)
Top Results From Across the Web
How to fix 'Unchecked runtime.lastError: The message port ...
I disabled all installed extensions in Chrome - works for me. ... message-passing apparatus) is closed before the 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 >Unchecked runtime.lastError: The message ... - Google Groups
I am new to chrome extension and was working over a project of chrome extension in manifest v3, while using messaging I faced...
Read more >"The message port closed before a response was received ...
If a browser.runtime.onMessage callback does not return a Promise, browser.runtime.sendMessage will be rejected with the following error, ...
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 >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
FYI: A new chrome release will be made for this. Might take a while due to weekends and someone had uploaded the wrong binary as the new “Version” so the next release might not be the one with the fix.
Currently also having this issue. From a web developer point of view, I thought something was wrong with my code when I opened the DevTools and spent time figuring out it was just the Dark Reader; I would appreciate having this bug fixed so I don’t see an error when I am working in the DevTools Console.
I rely on Dark Reader rather heavily, so I am willing to make time this weekend to start looking into this for a possible patch, but only if someone is able to point me in the correct direction so I’m not chasing my own tail.