Firefox extension slow

System · August 2021

This discussion was created from comments split from: Chrome Extension too slow to open.

yulmathieu · August 2021

I have the same issue with the Firefox extension. It frequently takes upwards of 15 seconds to get started.
This started happening when the feature about unlocking with Windows Hello was added.

ag_ana · August 2021

Hi @yulmathieu!

Can you please confirm what version of the 1Password desktop app and of the 1Password browser extension you are using?

yulmathieu · August 2021

My extension is 2.05, windows app is 7.7.810. I have noticed this issue on laptop that don't have the Windows app installed as well.

ag_ana · August 2021

@yulmathieu:

Thank you for the confirmation. I have split the discussion into a separate one, since the original poster was using the Early Access app, while you are using version 7 :+1:

Can you please send us some logs so we can take a closer look for you?

After you have sent the email, please feel free to post the ticket number you received so we can locate your message and connect it with this forum discussion.

Looking forward to your message!

yulmathieu · August 2021

I’m trying to paste logs but the comment stays in draft

yulmathieu · August 2021

Here's the firefox extension log

08:19:25.163 [OP] Locked at Thu Aug 05 2021 08:19:25 GMT-0400 (Eastern Daylight Time) background.js:2:1814779
08:24:02.519 📤 Sending <NmShowUnlock> message to native core <3863766229> background.js:2:1790470
08:24:02.551 📥 Received message <Nothing> from native core <3863766229> background.js:2:1789351
08:24:16.274 Received <LockStateChanged> from the native core background.js:2:1790035
08:24:16.275 📤 Sending <NmRequestAccounts> message to native core <2515728252> background.js:2:1790470
08:24:26.291
Failed to request accounts in requestAndUnlockAccountsFromApp: 
Object { type: "Timeout", content: "Timeout waiting for response to <NmRequestAccounts>" }
background.js:2:1794744
    requestAndUnlockAccountsFromApp moz-extension://XXX/background/background.js:2
08:24:26.291 When requesting accounts we ran into a problem background.js:2:1795668
08:24:26.291 📤 Sending <NmShowUnlock> message to native core <4051542975> background.js:2:1790470
08:24:28.547 Not attempting to connect to desktop app: already connected or connecting to desktop app background.js:2:1820782
08:24:36.306 Unable to show the unlock screen 
Object { type: "Timeout", content: "Timeout waiting for response to <NmShowUnlock>" }
background.js:2:1820703
08:24:36.321 📤 Sending <NmShowUnlock> message to native core <4125990026> background.js:2:1790470
08:24:37.794 Received <LockStateChanged> from the native core background.js:2:1790035
08:24:38.416 📥 Received message <Nothing> from native core <4125990026> background.js:2:1789351
08:24:38.417 📤 Sending <NmLockState> message to native core <2581834130> background.js:2:1790470
08:24:38.418 Received <LockStateChanged> from the native core 3 background.js:2:1790035
08:24:39.192 📥 Received message <NmLockState> from native core <2581834130> background.js:2:1789351
08:24:39.192 📤 Sending <NmRequestAccounts> message to native core <1587353985> background.js:2:1790470
08:24:39.194 📥 Received message <NmRequestAccounts> from native core <1587353985> background.js:2:1789351
08:24:39.208 📤 Sending <NmRequestAccounts> message to native core <2408876355> background.js:2:1790470
08:24:39.354 📥 Received message <NmRequestAccounts> from native core <2408876355> background.js:2:1789351
08:24:39.368 📤 Sending <NmLockState> message to native core <787081125> background.js:2:1790470
08:24:39.369 Hooray!; Unlocked account XXX with MUK; 🎉 background.js:2:1787191
08:24:39.371 We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). background.js:2:1795526
08:24:39.660 Hooray!; Unlocked account XXX with MUK; 🎉 background.js:2:1787191
08:24:39.661 We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). background.js:2:1795526
08:24:40.066 📥 Received message <NmLockState> from native core <787081125> background.js:2:1789351
08:24:40.159 📤 Sending <NmRequestAccounts> message to native core <942627942>

Here's 1password log:

21216  2021-08-05 12:24:03  0.000s     INFO  opw_app::app:196 > starting unlock role C:\Users\XXX\AppData\Local\1Password\app\7\1Password.exe v7.7.810
19060  2021-08-05 12:24:20  0.000s     INFO  opw_app::app:174 > starting cloud sync role C:\Users\XXX\AppData\Local\1Password\app\7\1Password.exe v7.7.810 for account XXXX
19060  2021-08-05 12:24:21  0.104s     INFO  opw_app::sync::sync_session:59 > account XXXX; type: F; session: XXX
19060  2021-08-05 12:24:21  1.728s     INFO  opw_app::sync::authorized_session:275 > Session XXX HTTP GET https://my.1password.com/api/v1/overview?__t=1628166261.763
19060  2021-08-05 12:24:22  1.730s     INFO  opw_app::sync::authorized_session:275 > Session XXX HTTP GET https://my.1password.com/api/v1/vault/XXX/534/items?__t=1628166262.016
19060  2021-08-05 12:24:22  1.983s     INFO  opw_app::sync::sync_session:741 > updating item 2bqixqwj3berbjkd64bobg2i24
19060  2021-08-05 12:24:37  17.228s    INFO  opw_app::sync::authorized_session:275 > Session XXX HTTP GET https://my.1password.com/api/v1/user/mfa/config?__t=1628166277.573
19060  2021-08-05 12:24:37  17.540s    INFO  opw_app::sync::sync_session:115 > Sync for account XXXX has finished in 16.055 sec
15284  2021-08-05 12:24:02  303299.438sINFO  opw_app::browsers::b5x:230 > b5x/15 received NmShowUnlock
15284  2021-08-05 12:24:14  303310.125sINFO  opw_app::roles::main::unlock:76 > app unlocked with master password
15284  2021-08-05 12:24:14  303322.281sINFO  opw_network::proxy:127 > loaded AutoDetect proxy - address: false, username: false, password: false
15284  2021-08-05 12:24:14  303322.375sINFO  opw_app::watchtower::compromised_sites:39 > loaded 4975 compromised websites in 21ms
15284  2021-08-05 12:24:15  303322.406sINFO  opw_network::proxy:175 > network connection test successful
15284  2021-08-05 12:24:15  303322.906sINFO  opw_network::proxy:55 > AutoDetect network proxy detection enabled
15284  2021-08-05 12:24:17  303322.906sINFO  opw_app::managers::item_manager:782 > downloaded compromised sites list in 519ms
15284  2021-08-05 12:24:19  303324.594sINFO  opw_app::managers::cloud_sync_manager:400 > initiating sync for all accounts...
15284  2021-08-05 12:24:19  303327.344sINFO  opw_app::managers::cloud_sync_manager:341 > starting sync for account XXXX
15284  2021-08-05 12:24:22  303327.344sINFO  opw_app::hub::notification_listening:241 > notifier connected for account XXXX
15284  2021-08-05 12:24:36  303329.562sWRN   opw_app::managers::item_manager:249 > message handler on_refresh_from_database took 21416ms to work
15284  2021-08-05 12:24:36  303343.750sINFO  opw_app::browsers::b5x:136 > b5x/15 received NmRequestAccounts (version: 1)
15284  2021-08-05 12:24:37  303343.781sINFO  opw_app::watchtower::compromised_sites:39 > loaded 4975 compromised websites in 4ms
15284  2021-08-05 12:24:37  303344.906sINFO  opw_app::browsers::b5x:230 > b5x/15 received NmShowUnlock
15284  2021-08-05 12:24:38  303345.344sINFO  opw_app::browsers::b5x:230 > b5x/15 received NmShowUnlock
15284  2021-08-05 12:24:39  303345.969sINFO  opw_app::browsers::b5x:213 > b5x/15 received NmLockState
15284  2021-08-05 12:24:39  303346.750sINFO  opw_app::browsers::b5x:136 > b5x/15 received NmRequestAccounts (version: 1)
15284  2021-08-05 12:24:39  303346.750sINFO  opw_app::browsers::b5x:136 > b5x/15 received NmRequestAccounts (version: 1)
15284  2021-08-05 12:24:39  303346.812sINFO  opw_app::browsers::b5x:213 > b5x/15 received NmLockState
15284  2021-08-05 12:24:39  303347.031sINFO  opw_app::managers::cloud_sync_manager:450 > account XXXX synced in 20104ms
15284  2021-08-05 12:24:40  303347.469sINFO  opw_app::browsers::b5x:136 > b5x/15 received NmRequestAccounts (version: 1)
15284  2021-08-05 12:24:40  303347.719sINFO  opw_app::browsers::b5x:136 > b5x/15 received NmRequestAccounts (version: 1)

It looks like the app stalls while trying to get an update from the 1password servers.

ag_yaron · August 2021

Hey @yulmathieu ,
Thanks for providing the logs.

We're investigating the matter and it does seem to occur for some users when the integration between the desktop app and the extension is enabled. The desktop app seems to be delaying when it tries to sync data.

For now, you can disable the integration from the extension's settings menu:

Open your browser.
Right click the 1Password extension menu and select "Settings".
Scroll down to the "General" section and turn off the "Integrate with 1Password app" option.

You'll lose Windows Hello unlock but the extension will respond much quicker, so it is up to you.
If we need any further info from you we'll let you know :)

ref: dev/windows/opw#5051

yulmathieu · August 2021

Thanks for the tip

ag_ana · August 2021

On behalf of Yaron, you are very welcome :+1:

Firefox extension slow

Comments