1Password for Safari on iPadOS/iOS: High CPU usage

An update: I managed to fix this on my iPad without reinstalling 1Password. I connected it to my Mac and inspected the Safari extension through remote Web Inspector.

This was with 1Password 8.12.36, extension version 8.12.36.40, on iPadOS 27.0.

Here’s what I found:

• The extension’s IndexedDB database, b5x, was at schema version 21 but had zero object stores. The code expects 17 stores, including accounts.
• Account reads were failing with NotFoundError. A fresh diagnostic report captured while the iPad was hot contained 1,594 “Failed to get accounts” messages in about 105 seconds.
• In background/database/connection.ts, _getDatabase() calls initDatabase() when the availability check fails. From reading the code, it appears to repeatedly open new connections and replace the database reference without closing the previous connection.
• Since the database was already at version 21, reopening it at that same version didn’t trigger the upgrade callback or recreate the missing stores.

The connection-handling explanation is my reading of the shipped code, so I’d appreciate confirmation from the developers.

To repair it, I temporarily paused the reopening loop, closed the retained database handles, deleted only the verified-empty b5x database, and reloaded the extension. I didn’t modify the native app database or make any permanent code changes.

The extension then recreated all 17 stores, finished initializing, and loaded my account. The database-error loop stopped, a follow-up live capture showed no errors, and CPU activity was low. The extension is working again now.

I still don’t know why the stores disappeared in the first place, and I don’t recall changing any relevant settings before the problem started.

I have the before/after database metadata, relevant source excerpts, and verification results available.