1Password causes major performance degradation

RageLtd

Woohoo, thank you laiz

I was just coming to report my experiences with github in Orion with 1Password:

Good news, anecdotally (sample size 2) it doesn't seem any worse off than Safari! On one big PR (143 files, ++8k --2.5K) it still has the classic Webkit "Wait for two seconds while the textarea renders and 1password hooks into it". I really wish either the Webkit folks or Github would do something about their transform-based layout, it runs like hot garbage on non-chromium.

In other hot garbage news, I forgot how smooth Orion's video playback is.. almost looks unnatural compared to Chromium/Arc

RageLtd

DBLClick So I also had this issue with my Orion profile - for whatever reason the Primary profile (the one that's synced across devices) just won't let me interact with the 1pass extension at all. I had to create a fresh profile (manage profiles -> new -> clean preset) for it to let me interact with the extension

DBLClick

That appears to resolve the issue with accessing the 1password, and performance is improved.

Still testing the dev build, hoping it continues to improve.

RageLtd

@laiz: Do you know if the latest RC (released today, 1.0.4.143.2) has the fixes from that dev build in it?

RageLtd

It certainly seems like no, based on its Speedometer behavior

rogue

1Password still takes a very long time to unlock in Version 1.0.4 (143.2.2-rc), WebKit 624.1.7

Browser also still excruciatingly slow.

RageLtd

Interestingly one of my major pain points seems to have been partially addressed in webkit commits that haven't been integrated into Orion just yet! The rendering of Github's diff page (with TWO experimental flags enabled) is much better on STP.

Now the remaining blocker (for me) is LastPass' OIDC callbacks when you log in with a Microsoft account.

laiz

The fixes should be live on Orion Version 1.0.4 (143.3-rc), WebKit 624.1.7 Build date March 12, 2026.
Please let us know how 1PW behaves on this version.

sparselogic

laiz 1PW behavior is much improved!
Too early to say that everything is perfect, but it's a big quality-of-life improvement for sure. Thank y'all!

RageLtd

Thanks so much laiz and the rest of the team!

Now I have one remaining blocker for Orion being my primary browser - just submitted the bug because I haven't seen it reported yet

RichieB

I am running 1.0.4 (143.3-rc) and it has the same issue as the other RC versions: when I leave Orion RC open (as I alsways do) and come back to it later, 1Password is locked. It offers to unlock it with my finger print which succeeds. The 1Password app is now unlocked. Orion RC fails to notice this and keeps showing the blue "Open 1Password" button. There is nothing I can do to make it notice 1Password is already unlocked, except restarting Orion RC.

nrudnyk

@RichieB would you be able to create a detailed report in separate post for better tracking so it doesn't get lost. Thanks!

RichieB

nrudnyk I'll make a new report when I run into it again.

DBLClick I just tried this: when coming back to my MacBook, go to the running 1Password app first, unlock it. Only then go to Orion RC. 1Password shows unlocked and is fully usable. In my previous tests where it showed locked it also did not offer the passwords that I needed on a website I opened.

DBLClick

This behavior I noticed. If you unlock 1PW using Orion, it does show locked. but functions normally. Entering Into Orion with 1PW is opened from desktop app or another browser is shows open. I always believed this was cosmetic.

sparselogic

RichieB this sounds similar to behavior i've encountered - behavior seems to vary based on whether you start by unlocking the 1Password app or the extension. But I've noticed improvement since the latest changes.

« Previous Page