Chrome autofill delays - repeated native messaging timeouts and XPC 4099 errors

Hi 1Password Support,

I’ve been experiencing significant delays with the 1Password Chrome extension on macOS.

When I focus on a username/password field, the 1Password autofill suggestions can take several seconds to appear. In some cases the extension appears to stop responding temporarily.

Environment:

• macOS: 26.6.1
• Google Chrome: 151.0.7922.174
• 1Password Desktop: 8.12.33 (build 81233001)
• 1Password Chrome Extension diagnostics build: 81234034

I’ve attached diagnostics from both the Chrome extension and the 1Password Desktop app.

I did an initial comparison of the two diagnostics and noticed what appears to be significant instability/latency in the native messaging / XPC communication path between the browser extension and the desktop app.

On the extension side, there are repeated native request delays such as:

• NmRequestAccounts: ~4,053 ms
• NmRequestAccounts: ~7,029 ms
• NmRequestAccounts: ~9,421 ms
• NmRequestDelegatedSession: ~6,151 ms
• NmRequestMacNativeAutofillStatus: ~5,354 ms
• NmLockState: ~8,336 ms

There are also repeated failures such as:

“Timeout waiting for response to ”

and:

“Failed to request accounts in requestAndUnlockAccountsFromApp”

The extension logs additionally contain messages such as:

• “Promise timed out. Collect Field Context”
• “Failed to get frame manager configuration”
• “Exception while handling request ”
• “Exception while handling request ”

The Desktop diagnostics appear to provide additional evidence around the browser integration path.

The BrowserSupport logs contain a very large number of the following XPC error:

“XPC-CoreFoundation: connection to extension helper received error: Domain NSCocoaErrorDomain:4099”

I counted approximately 1,018 occurrences of this error in the diagnostics.

The BrowserHelper logs also repeatedly show the extension/browser-helper connection being established and subsequently disconnected:

“Extension <-> browser helper connected”

followed by:

“Sending message to Desktop app”

and later:

“Extension <-> browser helper disconnected”

BrowserSupport also periodically reports:

“Reached end-of-stream for receiving messages from b5x. Ending SLS communication.”

followed by shutdown of the BrowserSupport process and, in some cases, NSCocoaErrorDomain:4099 errors.

One potentially useful correlation occurs around 2026-08-28 05:57 UTC.

The browser extension diagnostics show a native account request timing out around this period.

The Desktop diagnostics then show:

05:57:34
“Reached end-of-stream for receiving messages from b5x. Ending SLS communication.”

followed by:

“Shutting down 1Password-BrowserSupport”

and multiple:

“XPC-CoreFoundation: connection to extension helper received error: Domain NSCocoaErrorDomain:4099”

The Desktop app itself otherwise appears responsive during these periods. I only see occasional SQLite operations in the ~100–200 ms range, which doesn’t appear sufficient to explain the multi-second delays observed by the browser extension.

This makes me suspect that the issue may be somewhere in the communication path between:

Chrome Extension
→ 1Password-BrowserSupport
→ BrowserHelper/XPC
→ 1Password Desktop

rather than general Desktop app performance.

Could you please review both attached diagnostics and let me know whether these XPC 4099 errors and native messaging timeouts correspond to a known issue?

I’m particularly interested in whether this could be related to the current Chrome version or a recent change in the 1Password browser integration/native messaging implementation.

Thanks,
John