After closing 1Password Beta, the process lingers
in Linux Beta
After running the beta, if I close it, the process lingers.
I'm not sure what it's doing, but it just keeps running, eating up about 8% CPU.
I ran 1password from a terminal, and when I closed it, the terminal did not show a prompt again, which indicates the process is still running. I check with top, and that's the case, it was still running and doing something.
Including output in case anythere there is relevant:
$ 1password INFO 2020-11-22T23:51:42.541 op_executor:invocation_loop [op-app/src/app.rs:128] App::new(<redacted>/<redacted> (EN_US), Some(<redacted>)) INFO 2020-11-22T23:51:42.683 tokio-runtime-worker [op-db/src/sqlite/db.rs:93] Database is being created at <redacted> INFO 2020-11-22T23:51:42.747 op_executor:invocation_loop [op-app/src/app/backend/config.rs:33] Settings changed. INFO 2020-11-22T23:52:42.773 op_executor:invocation_loop [op-updater/src/lib.rs:86] Checking for updates... INFO 2020-11-22T23:52:42.773 op_executor:invocation_loop [op-updater/src/lib.rs:87] No updates were found for <redacted> channel. INFO 2020-11-23T00:01:15.073 op_executor:invocation_loop [op-b5-client/src/internal/unauthorized_session.rs:68] registered device <redacted> INFO 2020-11-23T00:01:29.958 op_executor:invocation_loop [op-b5-client/src/internal/unauthorized_session.rs:417] 2FA authentication completed, 2FA token is now in system keyring INFO 2020-11-23T00:01:31.610 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:31.780 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:32.957 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:34.209 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:35.301 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:35.517 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:37.003 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:37.869 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:38.121 op_executor:invocation_loop [op-syncer/src/sync_job.rs:839] Updated <redacted> items in vault <redacted> INFO 2020-11-23T00:01:38.298 op_executor:invocation_loop [op-data-layer/src/load.rs:265] loaded <redacted> items in <redacted> vaults for account: <redacted> ERROR 2020-11-23T00:01:38.324 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:116] NotImplemented INFO 2020-11-23T00:01:38.324 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:125] Lock state changed: Unlocked INFO 2020-11-23T00:01:38.341 ThreadId(74) [client:typescript] Lock Manager started. WARN 2020-11-23T00:01:39.126 op_executor:invocation_loop [op-app/src/app/backend.rs] operation invoke: Invocation(External(item-details)) on op-app/src/app/backend.rs:140 took more than 50 ms (51 ms) INFO 2020-11-23T00:01:43.577 op_executor:invocation_loop [op-data-layer/src/load.rs:50] reloading data layer... INFO 2020-11-23T00:01:43.685 op_executor:invocation_loop [op-data-layer/src/load.rs:265] loaded <redacted> items in <redacted> vaults for account: <redacted> INFO 2020-11-23T00:01:44.375 op_executor:invocation_loop [op-data-layer/src/vault.rs:153] Created system vault for account (<redacted>) INFO 2020-11-23T00:01:45.188 op_executor:invocation_loop [op-data-layer/src/load.rs:50] reloading data layer... INFO 2020-11-23T00:01:45.342 op_executor:invocation_loop [op-data-layer/src/load.rs:265] loaded <redacted> items in <redacted> vaults for account: <redacted> INFO 2020-11-23T00:02:06.694 op_executor:invocation_loop [op-app/src/app/backend/frontend.rs:11] Front end event: window closed ^C%
Actually, after pasting the log, I noticed that it did register the window closing. So it seems there's a bug somewhere and the process looping doing something. I'd be happy to help debug this further.
1Password Version: 0.9.4_1-1
Extension Version: n / a
OS Version: ArchLinux
Sync Type: Not Provided
Comments
Team Member
Hi @WhyNotHugo,
Thanks for reporting this. I haven't been able to reproduce this. Does this happen consistently every time?
Just to ensure we're on the same page here; closing the window doesn't close the process if you have system tray support enabled, it can still run in the background. You can run the 1Password command again while it was already running but I don't see that in your log because it would've log that it was shutting itself down as the first one is already running.
Did you see 1Password icon in your system tray area when this was happening? Also, try to terminate the 1Password process completely with your task manager and then run 1Password command in terminal this time, see if closing the terminal stops the process now.
As for the high CPU usage while idle, this is something we're still trying to figure out as it has been reported by some of our users in this thread.
Hi!
Yes, it happens consistently every time without exception.
I'm not using any form of tray or anything alike. It seems like tray-detection might be failing with a false-positive?
Anything I can do to help debug this further?
Thanks!
Team Member
Nope, I think your report has helped a ton!
We've opened an issue for this internally, and our team is looking into what's going on. I'll update you here once we get to the bottom of things. 💙