Confluence page loading fails with "This page was in the background for too long and may not have fully loaded. Try to refresh the page"
Observed:
I use Firefox 133 on Mint 22, I have 2 browser profiles. When I access Atlassian Confluence (any confluence page under atlassian.net), the page content is loaded, but then disappears and I get the following error at the top of the page: "This page was in the background for too long and may not have fully loaded. Try to refresh the page"
This only happens in one browser profile: in the other, all the pages open correctly and quickly. When I open a private tab using the problematic browser profile, again all the pages open correctly.
I have tried clearing all atlassian.net and atlassian.com cookies and data from the browser privacy settings, disabling all extensions, restarting the browser, even restarting the computer, but to no effect.
Expected: Confluence pages should open using any browser profile.
Reproducibility: 20+ out of 20+ attempts
Workarounds:
Temporarily use the other browser profile or a private tab, although that way I don't have the benefit of using browser history and if I kill the browser while using private tabs, private tabs will not be restored, so I lose track of what I was working on. I could use a different browser for confluence, but that has the same history problem and is generally senseless: Confluence should work correctly using any browser.
Notes:
I have seen similar issues 3-4 times before with Confluence, but it was always due to extensions, so disabling the problematic extension or configuring it to ignore anything related to Atlassian was sufficient. I would report this to Atlassian, but they'll just say "it works with a blank browser, so it's not our bug" and they're probably right. There's some kind of Atlassian-related state being preserved in the problematic browser profile, but I can't pinpoint it, so any help there is welcome.
All Replies (1)
Apparently, <Ctrl>-<F5> was what was needed to load the pages properly. This is not the first time I've wasted time on this: there should be a mechanism for a page to force a reload like that if something in the page code changed.
In any case, case closed, but now there's a reasonably easy to do, but not necessarily reasonably easy to find fix, so no further action needed.