1password mini keeps discrete graphics on...only sometimes?
I have a 2010 Macbook Pro with dynamic switching graphics. I'm using gfxcardstatus to inform me about whether the Intel or Nvidia GPUs are in use. On this particular laptop the Nvidia graphics cause a pretty significant drain on the battery. I've noticed that at some point during operation 1password mini keeps the Nvidia graphics engaged. If I fire up the main 1password4 app, then hold down Alt and select quit to kill both 1password and 1password mini the Intel graphics turn back on. I can then fire up the main 1password4 app, which turns on the Nvidia graphics and also 1password mini. When I quit the main app, the Intel graphics come back on but 1password mini is still running.
I hope that made sense. In general, 1password mini seems to be causing the Nvidia graphics to come on, but only sometimes. Killing 1password mini and restarting it switches back to Intel.
Any ideas?
Comments
-
Hi @adam2104,
Sadly, this is a known issue, under the Misc section on the bottom. This is a bug in the OS X drivers for those GPU setups in '09/'10 MBPs specifically. There isn't a workaround for this that we can do in our coding as we also had this bug in 1Password 3. Considering that Apple hasn't fixed it, it doesn't look like there will ever be a fix for this.
Generally, if you unlock the main 1Password app first before unlocking the mini, it should avoid triggering the dGPU. Can you confirm that, first log out and back in, open the main 1Password app and unlock it. It should retain the iGPU level.
0 -
Check this, possibly related:
http://discussions.agilebits.com/discussion/16064/known-issues-in-1password-4-for-mac"if you're using a 2010 MacBook Pro, using 1Password may trigger the dGPU to turn on. There isn't a workaround for this as it is an OS X issue, this issue also appears in 1Password 3."
There are issues with other software, related to dynamic graphics card switching, so I tend to believe Agilebits that it is an OS X problem.
Edit: MikeT posted an answer while I was typing mine.
0 -
Bummer. Shame on me for missing it in the Misc. section there. Sorry for the noise. This isn't the first 2010-specific issue I've encountered with this machine. sigh
0 -
Ah this is a shame, I've never seen it happen with 1Password 3.
Though maybe thats because I don't have the menu bar icon enabled (on both 3 and 4), and somethings changed with the way it works.
I'm on a mid-2010 MBP as well.Is there any chance of this being fixed?
Forcing the use of only the iGPU isn't really an option.Its more of a pain compared to other applications, as all the other apps that I've used which trigger it you can just close them down normally to cause the OS to switch back, in this case it seems you have to manually kill 1password mini.
0 -
Did you use the advanced setting in 1Password 3 to disable animations?
0 -
Yes, I'm pretty sure under 1Password 3 I had animations disabled, though it still triggered the dGPU when the main application was open, which I don't mind as it would release the dGPU once it was closed.
Under 1Password 4 I see in the settings under Browser there is an option for "Animate form filling" which I had missed the last time I looked. It was checked, so I've just unchecked it. Maybe this will help.
0 -
Unchecking the "Animate form filling" option hasn't helped, it still seems to be switching to the dGPU.
On closer inspection the switch to the dGPU appears to be triggered at the same time as the unlock animation of the Safari plugin (I haven't tried with any other browsers).0 -
I also have a 2010 17 inch MBP, and on 1Password3 I was able to live with this because I could disable the 1Password mini completely and the browser helper apps didn't require its use. I haven't found a way to not use the mini version as the helper apps seem to want to use it. Any help would be appreciated. Thanks
0 -
Seems like the easiest workaround at the moment is to just kill the "1Password mini" process (either from activity monitor or from the terminal) after each time you use the browser plugin.
I might try and schedule it to be automatically killed every few minutes so I don't need to do it manually, as I can't see any way to trigger it.
Either that or I'll have to work out how to revert back to version 3 (MAS purchase), which is an annoyance in itself as I bought it back in 2011 when it was going to be the only way to get version 4, and there was of-course no mention that it wouldn't work with Lion (bit unfair on the devs maybe because ML wasn't around then) on my older Mac Pro.
0 -
Hi guys,
"Animate form filling" which I had missed the last time I looked. It was checked, so I've just unchecked it.
That's just animating the filling in the browsers, it doesn't trigger the dGPU at all.
On closer inspection the switch to the dGPU appears to be triggered at the same time as the unlock animation of the Safari plugin (I haven't tried with any other browsers).
It's the same front end for all browsers, we're calling on 1Password mini to display its UI in any browser you use.
The only thing we can confirm from other users, is that the unlocking of the 1Password mini triggers the dGPU, We haven't been able to find a fix just yet. We'll keep looking but we have limited choices since this is a driver issue for those setups.
Seems like the easiest workaround at the moment is to just kill the "1Password mini" process (either from activity monitor or from the terminal) after each time you use the browser plugin.
What happens if you unlock using the main 1Password app first, not the mini. Does that then fix the problem as you use the browser? We've gotten reports from users that if you unlock the main app first, it doesn't trigger the dGPU since there's no unlock animation in mini.
I'll have to work out how to revert back to version 3 (MAS purchase), which is an annoyance in itself as I bought it back in 2011 when it was going to be the only way to get version 4
If you email us your proof of purchase at support+forum@agilebits.com, we can give you the website version for 1Password 3 instead.
there was of-course no mention that it wouldn't work with Lion (bit unfair on the devs maybe because ML wasn't around then) on my older Mac Pro.
The development of 1Password 4 started on Mountain Lion, that's why it requires Mountain Lion, we took advantages of all the latest APIs and security changes that Apple made.
Apple's updating their Mac App Store soon to let Lion or previous customers download compatible apps from Mac App Store, just like they did for the iOS App Store. So, that should theoretically let you download 1Password 3.9.x on Mac Pro.
0 -
What happens if you unlock using the main 1Password app first, not the mini. Does that then fix the problem as you use the browser? We've gotten reports from users that if you unlock the main app first, it doesn't trigger the dGPU since there's no unlock animation in mini.
Yes thats correct, if you use the main app first it does not trigger the dGPU as it is already unlocked in 1Password mini. But this isn't permanent as, once it times out and locks you need to use the main app again to unlock otherwise it will trigger the dGPU. So yes it does seem to either be triggered by the unlock animation or something else that happens at the same time.
Apple's updating their Mac App Store soon to let Lion or previous customers download compatible apps from Mac App Store, just like they did for the iOS App Store. So, that should theoretically let you download 1Password 3.9.x on Mac Pro.
I'll wait and see whether this happens then.
Thanks for the reply.
0 -
Great, thanks for the confirmation. We'll find a way to disable the animation in the mini and see if that'll fix the problem.
0 -
This will be great since killing 1Password mini is also not a really good solution ...
0 -
We agree, pti'Luc. :)
0 -
+1. I'm constantly having to kill mini. It's spoiling my experience of an otherwise great piece of software.
0 -
Which version of 1P4 are you running, Darren?
Of related interest, here's something @MartyS posted:
… for myself and several others the later versions have provided complete relief from graphics processor switching due to the animation changes AgileBits made. Please make sure that you're running the latest version: 4.0.9 from the AgileBits web site works for me.
0 -
Actually, no. Still using high performance graphics on my MBP late 2010. Mavericks latest looking at Activity Monitor.
0 -
Mini still requires high performance graphics. It's the helper onepassword-osx-helper according to gfxStatus
0 -
I have a similar issue, but it seems that version 4.0.9 acts as it should (with discrete graphics). When I updated to 4.1.1, the problem came back, so I chose to revert back to 4.0.9. Whatever changed in the most recent update brought back the graphics problem back.
0 -
Thanks for the additional feedback, guys.
It appears there's a dGPU-triggering regression in 4.1/4.1.1 and I've mentioned this to our developers.
0 -
FWIW. 1PW 4.0.9 didn't fix it for me. Mid 2010 MBP running OSX 10.8.5. 1Password agent fails to release the discrete gpu once it switches from the integrated gpu.
0
