"This page was reloaded because of a problem" on every page when using latest Safari extension

Ryan_Parman Glad things are working well now! Please feel free to reach back out again if you need help. Have a good one!

This is fixed for me in the most recent update. Thanks!

IMO, feel free to close.

Hey Ryan_Parman / @felixfbecker:

We're aware of this and how frustrating it is, and are readying to submit a fix with our next release of 1Password for Safari. Thanks for your patience!

Jack

ref: dev/core/core#13200

1. Opened Develop → Web Extension Background Pages → 1Password for Safari — Background Page, which opened the Web Developer Console in a new Window.
2. In my original window, I selected one of the domains that had failed for me: login.live.com.
3. Clicked the result in the 1P prompt attached to the username field; logged-in successfully and without crashing. (weird)
4. Selected a different domain (dashboard.stripe.com/login), and opened it in my original window.
5. Clicked the result in the 1P prompt attached to the username field; browser process crashed (expected).

Here is a screenshot of the Web Developer Console for the 1P background page:

Note that the yellow “Promise timed out” error message showed up just after the browser process crashed.

To add to the list of sites, these sites that I'm randomly pulling from my 1Password account. I copy the URL to my clipboard, and manually paste it into my browser (NOT using the "open and fill" functionality in 1P8):

• okta.com
• stripe.com
• dash.cloudflare.com
• plex.tv
• twitter.com (it DOES happen to me here)
• wordpress.com
• login.live.com
• delta.com
• reddit.com
• accounts.google.com

These sites appear to work for me without crashing:

• github.com
• en.wikipedia.org
• accounts.firefox.com
• login.opendns.com
• squareup.com
• evernote.com
• amazon.com
• letterboxd.com
• cloud.digitalocean.com
• sso.accounts.dowjones.com (via accounts.wsj.com)
• washingtonpost.com
• login.ubuntu.com

While putting together this list, I've noticed a pattern that is allowing me to predict (with about ⅔ accuracy) which logins will crash before I attempt them:

1. It is MORE likely that a login page will crash when it asks for username + password on the same page.
2. It is LESS likely that a login page will crash when it asks for username then password on separate pages.
3. This is not universal.

I've been running into this issue since mid-February. I'm using 1P8 (latest beta) and https://apps.apple.com/us/app/1password-for-safari/id1569813296?mt=12 with Safari Technology Preview [Release 140 (Safari 15.4, WebKit 17614.1.1.5)]. This issue is specific to the pairing of Safari (or STP) with the external 1Password for Safari browser extension.

Typically, it will first crash the tab and report that "the webpage reloaded because an error occurred", then will subsequently (and sometimes automatically) perma-crash the tab (i.e., Safari will stop bothering to try) and report "A problem repeatedly occurred with {URL}." It happens in cases where the username/password field shows the 1P prompt with the list of credentials. As soon as you select a credential, the browser process crashes.

The biggest frustration for me is Okta (used for work, which means I get aggressively logged-out), but I'd estimate it happens on probably 90%+ my login attempts (which is different from the number of unique websites I visit). Generic Apple Support Community links will not be helpful as it is clearly either a bug in the 1P extension, in Safari Technical Preview, or a problem in the interaction with multiple extensions together. But when doing the basic disable-extensions-until-you-find-the-problem process, it's always the 1P extension.

At first, I thought it was simply a bug in that beta version of 1P8 that wasn't playing nicely, or maybe a bug in that version of STP, but both have had updates since this issue first showed up for me in mid-February. The only one which hasn't is the 1P extension.

Hi kevin_li –

the suggestions in that post I see are to:
1. Clear the cache (which I already tried)
2. Clear all history
3. Delete cache file manually in system files
4. Disable extensions one-by-one

These options are very invasive – clearing my history would clear all autocomplete suggestions in the address bar, which I rely on daily for my workflow. Deleting a file from system files that essentially is just the same as clearing caches seems unnecessarily risky if emptying caches already didn't do anything.
And I already disabled extensions one-by-one and found out that it is specifically the 1Password extension causing this.
As such I am hesitant to try any step like deleting all my history if there is no indication that might fix it.

Speaking as a web software engineer myself, an error like this happens when JavaScript that runs on the page enters an infinite loop. If this only happens when 1Password is clicked in the UI, but never when the extension is off, then that means that it is JavaScript that 1Password runs on the page on click – meaning there must be a bug in the 1Password's extension's JavaScript code.

Are you able to reproduce this issue on your end in the same Safari version?

Hi, @felixfbecker.

Sorry to hear that it didn't work. I found a similar discussion with some further suggestions from Apple Support Community: Error: This webpage was reloaded because … - Apple Community.

Let us know if it helps.

Ah, sorry. No, emptying caches didn't help unfortunately.

@felixfbecker Not quite. These are the steps that Nhat sent on 2/14 that I'd like for you to try:

Hello @felixfbecker,

Thank you for letting me know and I am sorry for my carelessness. Can you confirm if this issue occurs on all sites or just some? Let us start with these steps to see how it works and go from there.

1. Launch Safari and go to Preferences.
2. Then click on Advanced.
3. Scroll down to Show Develop menu in menu bar.
4. Enable this option and click on the Develop tab.
5. Select Empty caches.
6. Restart Safari and try again.

Let us know how that goes!