1Password 7 affecting my laptop's battery life?

Hey guys, I'm currently trying to understand what causes battery drain on my laptop and I think 1Password 7 is a potential culprit. When measuring my energy efficiency with "powercfg /energy", I find that 1Password is explicitly requesting a timer resolution of 1 ms instead of the default 15,6 ms of Windows (logs to follow) which is a pretty bad practice for battery life as discussed here:

https://randomascii.wordpress.com/2013/07/08/windows-timer-resolution-megawatts-wasted/

Question: does 1Password really need to do that? Wouldn't be a way to avoid asking this explicit short timer resolution so as to maximize battery life (at least when on battery)? After all, we all run 1Password in the background and I wish this isn't one of these apps greedily draining my battery...

Sorry for the french logs below, but feel free to run "powercfg /energy" to get a similar report:

Résolution de la temporisation de la plateforme:Pile de demande de temporisation
Pile de modules responsable du paramètre de temporisation de plateforme le plus bas dans ce processus.
Période demandée
10000
ID de processus demandeur
13332
Chemin d’accès au processus demandeur
\Device\HarddiskVolume3\Users\fredg\AppData\Local\1password\app\7\1Password.exe
Pile du module appelant
\Device\HarddiskVolume3\Windows\SysWOW64\ntdll.dll
\Device\HarddiskVolume3\Windows\SysWOW64\kernel32.dll
\Device\HarddiskVolume3\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
\Device\HarddiskVolume3\Windows\SysWOW64\kernel32.dll
\Device\HarddiskVolume3\Windows\SysWOW64\ntdll.dll

The bold number above is expressed in ns.


1Password Version: 7.1.567
Extension Version: Not Provided
OS Version: Windows 10 April Creators Update
Sync Type: Not Provided
Referrer: forum-search:battery life

Comments

  • MikeT
    edited July 2018

    Hi @dodmcdund,

    Thanks for reporting this.

    It is a confirmed bug with our lock view, we're asking WPF (Windows Presentation Foundation, what you saw as \WPF\wpfgfx—v0400.dll in the logs) to produce a subtle effect on the blue ring but it turns out that it is using something else in the background that spins up the CPU constantly when the lock view is left behind. If you close the 1Password window, the CPU usage is gone. It's not our intention to do this, it's something we found out after we rebuilt the lock view and noticed it. It'll be fixed in a future update soon.

    For now, close the 1Password window when it is locked if you don't plan to use it for a while.

    ref: OPW-2189

This discussion has been closed.