1Password 7.7 very slow on 2018 MacBookPro running Catalina

markjreed
markjreed
Community Member
in Mac

My machine is lightly loaded - I have no foreground apps running but Terminal, Safari, and 1Password. The top command shows the system as >95% idle. I've rebooted recently, quit and relaunched both 1Password and Safari, and made sure the AppExtension process was restarted as well.

I hit ⌘\ to bring up 1Password. If my vault is already unlocked it pops up almost instantly, but if not, then nothing happens for about four seconds. After that interval I finally get the "1Password wants to unlock" dialog, beside the 1Password vault window showing the message "Scan Fingerprint" in the entry field. Since I'm using the machine in docked mode with an external keyboard, I hit the spacebar to activate the "Enter Master Password" button in the unlock dialog. This dismisses the dialog, and focus goes back to the Terminal window. And then nothing else happens for another four seconds, after which focus vanishes from the Terminal; typing goes nowhere for a second, then the field in the vault window finally changes to "Enter Your Master Password", a cursor appears, and focus is pulled into that field.

Eight seconds may not sound like a lot of time, but in the middle of an all-keyboard workflow it really slows things down. Also, if I get ahead of 1Password and start typing my master password immediately, that means I'm typing it into the Terminal as a shell command, where it is not only visible to anyone nearby (admittedly not much of a problem these past several months) but where it will be saved to my shell history if I make it as far as hitting the return key. As I'm typing this question, I'm seeing the same behavior even from within the browser; maybe that's not surprising, but for some reason I had thought the keyboard shortcut used a different path via the extension when triggered from a browser window. Anyway, from here if I just hit space and start typing the master password, I'm typing it into this message.

I get a similar delay if I click the 1Password icon in the menu bar, except then I also get a beach ball while waiting for the popup.

So any suggestions on how to speed things up would be appreciated. Is there some sort of defragmentation I can run on my password vault? I already emptied the Trash, but that didn't make any noticeable difference.

1Password Version: 7.7 (70700015) 1Password Store
Extension Version: 7.7
OS Version: OS X 10.15.7
Sync Type: 1Password.com account
Referrer: forum-search:"macOS" "popup" "master password" "focus"

Comments

  • drtimhill
    drtimhill
    Community Member

    I've seen this too. It seems to have happened with the 7.7 update on macOS Catalina 10.15.7

    -- Opening 1password takes about 2-3 times longer.
    -- Unlocking the main screen is also much slower.
    -- Edits to items on macOS always "beach ball" for 4-5 seconds after I click Save on the item being edited.

    Nothing that I'm aware of has changed on my laptop, and I've checked my network which is running at normal speed.

  • inmyhead
    inmyhead
    Community Member

    Hi, I'm also getting this performance problem.

    I switched to a brand new 16" macbook pro a few weeks ago and have been getting this issue with 1Password ever since the switch. I'm pretty sure that I used the exact same version of 1P on my old macbook without any issue.

    Unlocking takes > 30 seconds. Switching between items is sometimes instant but usually results in a spinning ball for half a minute. Switching between vaults and edit/save also causes a spinning ball. Activity Monitor shows 100% CPU and the text "Not Responding" when that happens.

    • 1Password Version 7.7 (70700015) - 1Password Store
    • macOS Catalina 10.15.6 (19G73)
    • Syncing to the EU cloud

    I'm on a corporate vpn but I get the same issue when I disconnect.

    I'm a big fan of 1Password and I hate to bring you bugs for Christmas :)
    Hope you can solve it easily.

  • JRM01
    JRM01
    Community Member

    I started experiencing these slow downs also, although on macOS Big Sur.

  • brian7
    brian7
    Community Member

    I was experiencing this as well on Catalina. I did a fresh install of Big Sur (for a number of reasons--including this), but unfortunately it didn't solve the problem. Still dealing with slow unlock speeds.

  • miguelferreira
    miguelferreira
    Community Member

    I started experiencing the same issues described here. In my case it doesn't matter if the vault is unlocked or not.

  • Thomas
    Thomas
    Community Member

    I am experiencing the same problems with 7.7 (download non-appstore version) at macOS 11.1 on an iMac Pro (iCloud Sync).

    Basically everything regarding unlocking and especially saving takes unberable long. Unlocking is about 10-15 seconds, saving a note with some text is sometimes about 60 seconds plus!!

  • jeremywsherman
    jeremywsherman
    Community Member

    I've run into this issue with slow unlocks. Version info:

    1Password 7
Version 7.7 (70700015)
1Password Store

ProductName:    Mac OS X
ProductVersion: 10.15.7
BuildVersion:   19H114

    Most recently, the UI seemed to lock up hard when I typed in the search field to search items after I'd recently added and deleted an item.

    Investigation

    I ran a process sample and spindump on the main app. It had a wacky number of threads - the sample reported "Dispatch Thread Soft Limit: 80 reached in 2381 of 2381 samples -- too many dispatch threads blocked in synchronous operations".

    The spindump called out all those blocked threads:

      Thread 0xd7a444,0xd7a564,0xd7a5c1,0xd7a5c2,0xd7a5c8,0xd7a7ed,0xd7a7f4,0xd7a857,0xd7a859,0xd7a85a,0xd7a85b,0xd7a85c,0xd7a863,0xd7a864,0xd7a865,0xd7a866,0xd7a867,0xd7a868,0xd7a869,0xd7a86a,0xd7a86b,0xd7a86c,0xd7a86d,0xd7a86e,0xd7a86f,0xd7a870,0xd7a871,0xd7a872,0xd7a873,0xd7a874,0xd7a875,0xd7a876,0xd7a877,0xd7a878,0xd7a879,0xd7a87a,0xd7a87b,0xd7a87c,0xd7a87d,0xd7a87e,0xd7a87f,0xd7a880,0xd7a881,0xd7a882,0xd7a883,0xd7a884,0xd7a885,0xd7a886,0xd7a887,0xd7a888,0xd7a889,0xd7a88a,0xd7a88b,0xd7a88c,0xd7a88d,0xd7a88e,0xd7a88f,0xd7a890,0xd7a891,0xd7a892,0xd7a893,0xd7a894,0xd7a895,0xd7a896,0xd7a897,0xd7a898,0xd7a899,0xd7a89a,0xd7a89b,0xd7a89c,0xd7a89d,0xd7a89e,0xd7a89f,0xd7a8a0,0xd7a8a1,0xd7a8a2,0xd7a8a3,0xd7a8a4    DispatchQueue "com.apple.root.default-qos"(10)    78000 samples (1-1000)    priority 37 (base 37)
  78000  start_wqthread + 15 (libsystem_pthread.dylib + 7031) [0x7fff73114b77]
    78000  _pthread_wqthread + 220 (libsystem_pthread.dylib + 10743) [0x7fff731159f7]
      78000  _dispatch_worker_thread2 + 92 (libdispatch.dylib + 69783) [0x7fff72eca097]
        78000  _dispatch_root_queue_drain + 326 (libdispatch.dylib + 67927) [0x7fff72ec9957]
          78000  _dispatch_queue_override_invoke + 763 (libdispatch.dylib + 17584) [0x7fff72ebd4b0]
            78000  _dispatch_client_callout + 8 (libdispatch.dylib + 9816) [0x7fff72ebb658]
              78000  _dispatch_call_block_and_release + 12 (libdispatch.dylib + 5828) [0x7fff72eba6c4]
                78000  ??? (OnePasswordUI + 1161598) [0x102ff697e]
                  78000  ??? (OnePasswordUI + 422240) [0x102f42160]
                    78000  ??? (OnePasswordUI + 536569) [0x102f5dff9]
                      78000  ??? (OnePasswordUI + 537769) [0x102f5e4a9]
                        78000  ??? (OnePasswordCommon + 1439000) [0x10455e518]
                          78000  -[OPWatchtower vulnerabilityForItemSpecifier:] + 196 (OnePasswordDatabase + 10460) [0x10475a8dc]
                            78000  _dispatch_sync_f_slow + 171 (libdispatch.dylib + 58771) [0x7fff72ec7593]
                              78000  __DISPATCH_WAIT_FOR_QUEUE__ + 287 (libdispatch.dylib + 59713) [0x7fff72ec7941]
                                78000  _dispatch_thread_event_wait_slow + 40 (libdispatch.dylib + 11449) [0x7fff72ebbcb9]
                                  78000  __ulock_wait + 10 (libsystem_kernel.dylib + 9566) [0x7fff7305755e]
                                   *78000  ??? (kernel + 6983824) [0xffffff80008a9090]

    And they seem likely to have been coordinated/blocked on these two threads, right below those in the spindump:

      Thread 0xd7a7de    DispatchQueue "com.agilebits.db.watchtower (QOS: UTILITY)"(168)    1000 samples (1-1000)    priority 20 (base 20)
  1000  start_wqthread + 15 (libsystem_pthread.dylib + 7031) [0x7fff73114b77]
    1000  _pthread_wqthread + 220 (libsystem_pthread.dylib + 10743) [0x7fff731159f7]
      1000  _dispatch_worker_thread2 + 92 (libdispatch.dylib + 69783) [0x7fff72eca097]
        1000  _dispatch_root_queue_drain + 326 (libdispatch.dylib + 67927) [0x7fff72ec9957]
          1000  _dispatch_async_redirect_invoke + 703 (libdispatch.dylib + 16150) [0x7fff72ebcf16]
            1000  _dispatch_continuation_pop + 414 (libdispatch.dylib + 18456) [0x7fff72ebd818]
              1000  _dispatch_client_callout + 8 (libdispatch.dylib + 9816) [0x7fff72ebb658]
                1000  _dispatch_call_block_and_release + 12 (libdispatch.dylib + 5828) [0x7fff72eba6c4]
                  1000  __NSOQSchedule_f + 182 (Foundation + 264041) [0x7fff3b525769]
                    1000  __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 17 (Foundation + 264345) [0x7fff3b525899]
                      1000  -[NSOperation start] + 722 (Foundation + 265075) [0x7fff3b525b73]
                        1000  __NSOPERATION_IS_INVOKING_MAIN__ + 17 (Foundation + 268609) [0x7fff3b526941]
                          1000  -[NSBlockOperation main] + 80 (Foundation + 268710) [0x7fff3b5269a6]
                            1000  __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 (Foundation + 268933) [0x7fff3b526a85]
                              1000  __37-[OPDatabaseManager updateWatchtower]_block_invoke + 293 (OnePasswordCommon + 859896) [0x1044d0ef8]
                                1000  -[OPWatchtower(ItemVulnerability) setVulnerabilityForOP4Items:b5Items:] + 913 (OnePasswordCommon + 349423) [0x1044544ef]
                                  1000  -[OPWatchtower hash] + 132 (OnePasswordDatabase + 8900) [0x10475a2c4]
                                    1000  _dispatch_sync_f_slow + 171 (libdispatch.dylib + 58771) [0x7fff72ec7593]
                                      1000  __DISPATCH_WAIT_FOR_QUEUE__ + 287 (libdispatch.dylib + 59713) [0x7fff72ec7941]
                                        1000  _dispatch_thread_event_wait_slow + 40 (libdispatch.dylib + 11449) [0x7fff72ebbcb9]
                                          1000  __ulock_wait + 10 (libsystem_kernel.dylib + 9566) [0x7fff7305755e]
                                           *1000  ??? (kernel + 6983824) [0xffffff80008a9090]

  Thread 0xd7a8a9    DispatchQueue "com.vluxe.starscream.websocket"(46334)    1000 samples (1-1000)    priority 37 (base 37)
  1000  start_wqthread + 15 (libsystem_pthread.dylib + 7031) [0x7fff73114b77]
    1000  _pthread_wqthread + 290 (libsystem_pthread.dylib + 10813) [0x7fff73115a3d]
      1000  _dispatch_workloop_worker_thread + 596 (libdispatch.dylib + 72713) [0x7fff72ecac09]
        1000  _dispatch_lane_invoke + 363 (libdispatch.dylib + 34262) [0x7fff72ec15d6]
          1000  _dispatch_lane_serial_drain + 597 (libdispatch.dylib + 31812) [0x7fff72ec0c44]
            1000  _dispatch_client_callout + 8 (libdispatch.dylib + 9816) [0x7fff72ebb658]
              1000  _dispatch_call_block_and_release + 12 (libdispatch.dylib + 5828) [0x7fff72eba6c4]
                1000  ___signalEventQueue_block_invoke + 18 (CoreFoundation + 1049178) [0x7fff38f2825a]
                  1000  _signalEventSync + 217 (CoreFoundation + 717021) [0x7fff38ed70dd]
                    1000  ??? (OnePasswordCore + 303256) [0x1032a1098]
                      1000  ??? (OnePasswordCore + 303059) [0x1032a0fd3]
                        1000  ??? (OnePasswordCore + 318526) [0x1032a4c3e]
                          1000  -[NSOperationQueue waitUntilAllOperationsAreFinished] + 229 (Foundation + 1113600) [0x7fff3b5f4e00]
                            1000  __NSOPERATIONQUEUE_IS_WAITING_ON_AN_OPERATION__ + 17 (Foundation + 1979008) [0x7fff3b6c8280]
                              1000  -[NSOperation waitUntilFinished] + 697 (Foundation + 331483) [0x7fff3b535edb]
                                1000  __psynch_cvwait + 10 (libsystem_kernel.dylib + 14466) [0x7fff73058882]
                                 *1000  psynch_cvcontinue + 0 (pthread + 18722) [0xffffff7f82b41922]

    Some of those symbols aren't published, but the devteam should be able to symbolicate them.

    I also created a 1Password Diagnostics Report at the same time.

    I'd be happy to send on over the diagnostics report, spindump, sample, and some screenshots I took of Activity Monitor if they'd be helpful.

    Analysis

    One possible issue is threadsplosion due to unbounded operation spawning while refreshing watchtower details. Since this looks to be using NSOperationQueue to coordinate, instead of messing around with semaphores, you should be able to set the queue's maxConcurrentOperationCount to some value that isn't -1.

    (This is akin to the issue introduced and then resolved in Mike Ash's 2009 "GCD Practicum" article. Things have gotten better in the decade since that was written: the machine didn't hardlock, just the app. :)

  • Beeeeeee
    Beeeeeee
    Community Member

    Yep, same problems since upgrading here. 30+ seconds to unlock the app.

  • Echobase43
    Echobase43
    Community Member

    I'm experiencing the same problems with slow performance on the Mac OSX desktop app. Normal operations of editing content result in 8-10 second beach ball lags. Unlocking 1PW from launch can take up to 20 seconds. This all started shortly after updating to Big Sur, and in the holiday season - could 1PW servers be experiencing high traffic due to folks trimming up logins during the holiday downtime?

    My configuration ...

    1Password 7
    Version 7.7 (70700015)
    1Password Store

    MacBook Pro (Retina, 15-inch, Mid 2014)
    MacOS Big Sur 11.1

    Hope 1PW ENG has a ticket open for this - product is becoming unusable.

  • boyEatsSteak
    boyEatsSteak
    Community Member

    Similar for me:
    1Password 7
    Version 7.7 (70700015)
    1Password Store
    macos 10.15.7

    Most of the time I "only" have to wait 2-3 seconds, not the 30 that some people are reporting, but I still find it bothersome. I really hope this can be resolved soon.

  • Echobase43
    Echobase43
    Community Member

    1PW tech support got back to me on this (sorry I didn’t reply earlier), and recommended I enable Beta test channels (via preferences). This has fixed the performance / memory drain problems I was experiencing. They apparently are working on a new production version of 1PW (not a beta build) that will resolve the Big Sur memory drain issue.

  • ag_tommy
    ag_tommy

    @Echobase43

    Yep, it's in the pipeline. Hopefully soon. I'm glad to hear you have much better results.

  • ag_tommy
    ag_tommy

    @boyEatsSteak

    If you'd like to give the beta a go please use this set of instructions.

    https://support.1password.com/betas/

  • Ben
    Ben

    Hi all,

    1Password 7.8 is now available from our website and contains the performance fixes that had been in the beta. If you installed the beta for the fix and want to get back on the non-beta release you can find instructions in this guide: https://support.1password.com/betas/

    Thanks!

    Ben

This discussion has been closed.