Pulsar Jolt

Thanks, Syd! I was experiencing similar performance issues and initially thought they were related to Google Drive syncing. Your findings pointed me in the right direction, and disabling AutoFill resolved the problem completely. Really appreciate you taking the time to investigate and share this. You saved me a lot of troubleshooting!

UPDATE: Found the culprit – macOS AutoFill was causing the slowdown I wanted to follow up and share that I finally found (Syd found) the cause of the performance issues I described above. What I initially believed to be Enpass synchronization problems with Google Drive turned out to be related to the macOS AutoFill integration. Thanks to Syd, who identified this issue and shared his findings, I disabled Enpass as an AutoFill provider in macOS System Settings. The difference was immediate. The excessive CPU usage and the delays I was experiencing disappeared. I want to thank Syd for taking the time to investigate this and share his findings. His post pointed me in the right direction and saved me from continuing to chase what I thought was a sync problem. For now, I'll be leaving Enpass disabled as an AutoFill provider until the Enpass development team addresses this issue. Hopefully, this helps other Mac users experiencing similar slowdowns, particularly those running Apple Silicon machines. The takeaway: If you're experiencing unusually high CPU usage or sluggish performance with Enpass on macOS, try disabling Enpass as an AutoFill provider in System Settings.

I'm experiencing some seriously excessive delays with Enpass on macOS, particularly during the initial sync with Google Drive. I'm seeing delays approaching 30 seconds, and this is with a vault containing only 412 items. That's simply not a reasonable expectation. ISP Spectrum at 300+ Mbps solid everywhere else. I've rebooted the MacBook several times, but the problem persists. At this point, I'm beginning to wonder whether Enpass needs more dedicated macOS development attention, or perhaps someone on the development team with deeper macOS expertise. For context, this is an M3 Pro MacBook Pro that performs exceptionally well with everything else I throw at it. Android Studio, VS Code, video playback, and other demanding applications all run extremely smoothly. There is nothing about this machine that suggests a general performance problem. The delays appear isolated to Enpass. Here are some examples of what I'm experiencing: Initial startup / Google Drive sync: Approximately 28–30 seconds. The application opens, displays the Touch ID unlock prompt, and then sits spinning while it attempts to connect and sync. Saving a new item: Approximately 24 seconds. Creating a new item and accepting the default: Approximately 9 seconds. I'm also noticing delays with practically anything that requires Enpass to access the vault stored on Google Drive. System Information: Enpass Version: 6.12.7 (2786) Enpass Premium Installation: Mac App Store MacBook Pro: 14-inch, November 2023 Processor: Apple M3 Pro Memory: 18 GB macOS: Golden Gate 27.0.1 Vault: Google Drive Vault size: 412 items I'd really like to understand what's happening here. Is this a known issue with the macOS version, Google Drive integration, or perhaps the way Enpass handles vault access and synchronization? I understand that cloud synchronization takes some time, but these kinds of delays for such a small vault are excessive. Enpass is supposed to be a fast, convenient password manager. Waiting 20–30 seconds for routine operations isn't something users should have to accept, particularly on modern Apple Silicon hardware. I think it's time for the macOS experience to receive some serious performance attention.