Forum Discussion
"The database was terminated." error message in the browser
Starting this morning, whenever I attempted to login to the Safari extension, it appears to crash with the message that the database maybe corrupted as the connection was terminated (will get a image to upload when it happens again). This even after having done the following:
- Checked that I am using the current version of 1Password for Safari (v2.10.0)
 - Am on the current most up to date version of Mac OS Ventura
 - Quit and restarted both Safari and 1Password
 
Even with all this, I am still getting the message (via a lovely full Safari page background. :))
Anyone else have this issue? I will restart my Mac as well (an M1 Mac mini) and provide feedback; but this is the first time I have seen this type of issue with the Safari extension.
Any feedback would be appreciated.
Anthony
1Password Version: 8.10.4
Extension Version: 2.10.0
OS Version: 13.3.1
Browser:_ Safari
76 Replies
- 1P_Tommy
Moderator
@klanchman
Thank you for the submission. Did you receive a support ID?
 - bogardOccasional Contributor
I have the same error after updating to extension. Kind of frustrating as I usually clear all history manually at the end of a Safari session. I contacted support, who said to press the option key while selecting clear history (which does not clear website data). This works, but it's irritating, and I hope this behavior is changed in future updates to the extension.
 - Former Member
I've been seeing this on 2 different computers. It only happens (so far) in Safari. It's usually after I've logged into App Store Connect and navigate around in there a bit. Once the error appears App Store Connect gets logged out and the 1Password extension stops working throughout Safari until I restart Safari or toggle the extension off/on.
@Joy_1P I tried to grab extension console logs, but when the error page appears the console window closes itself. I'm sending what I can manage to get to the email you mentioned đ
 - Former Member
I also have the database termination error on Safari history clearing. Never even seen this error in all the many years of using 1P. The error only started on the last update of 1P from the App Store. None of the suggested fixes worked.
 - steph_giles
1Password Team
You're welcome @Dub, let us know if there is anything else we can help with.
 - Former Member
Great.
Thank you! - 1P_Tommy
Moderator
@dub
Thank you for the feedback. The team is working to make the working better. I can't say that the message would not appear, but the team is looking into the best way to move forward.
 - Former Member
I, like many other folks I know always clear my history at least once a day before closing my browser. So, yes, you are correct that upon re-start everything was working just fine before and obviously everything works just fine now.
No workarounds are needed.
Bottom line: I clearly understand the change, but in my humble opinion, there should be no error message. The reasons are first that it is not an error, and second, that the message serves no useful purpose.
On top of that, the wording of the message is too ominous and confusing. The sentence in red, the words âwas unexpectedly terminatedâ and âmay have become corruptâ , as well as the recommendation to review your 1Password settings in the browser are way too ominous for something simple that is not an error.
I would recommend that the company eliminate the "error message" completely. It is clearly not needed and the words used are way too ominous and confusing to users.
Thank you again for your quick response and explanation. - 1P_David
1Password Team
You're welcome, @Dub! Were you previously clearing the history only before closing Safari? While the error message is new, clearing your history/cache in previous versions of 1Password for Safari would also clear the local copy of your information and you would be required to restart Safari in order to get things working normally again. If you had previously been clearing the history and closing Safari, once you relaunched Safari, things would be working as normal.
 - Former Member
Thank you for the link to the available workarounds.
I find it peculiar that 1Password never did this before the latest version. Sounds like you must have changed something in the way that 1Password operates with Safari.