Users reported a runtime error causing a blank screen when navigating to Discourse forums via links, with the error message: ‘Unchecked runtime.lastError: The page keeping the extension port is moved into back/forward cache, so the message channel is closed.’ Phil_Snow initially suspected a Discourse issue, referencing a specific commit. david asked for clarification on how users were navigating to the site and whether links were standard or JavaScript-driven. Phil_Snow confirmed the issue occurred via standard links and required a browser refresh to load content. david suggested the issue might be specific to the implementation or browser, asking for more details including browser versions and example pages. Ultimately, Phil_Snow identified the root cause as a Chrome extension — Jam — and considered the issue resolved. No Discourse bug was confirmed, and the problem appears isolated to users with this extension enabled.
On this meta forum and our Discourse hosted forum we are getting a runtime error when directing to the sites through URLs causing a blank screen with only basic background styling.
Unchecked runtime.lastError: The page keeping the extension port is moved into back/forward cache, so the message channel is closed.
It points to this commit:
Can you expand on what you mean by this? How are you directing people to the site? Via a link? Typing into browser address bar?
What URL are you directing people to?
Through links yes. I have to refresh the browser to get the content.
There must be something specific/unusual about your links. If all links to Discourse forums were broken, we would be getting a lot more complaints.
Can you share more about how the links are implemented? Are they just simple <a href=? Or is there some JS involved?
Can you share a page which demonstrates the problem?
Which browsers does this happen in?
Looks like it’s a browser extension in Chrome causing the issue. Specifically Jam.
You can consider this closed.