Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keybase utility changes Windows CPU timer resolution #2525

Closed
nscaife opened this issue Apr 4, 2016 · 6 comments
Closed

Keybase utility changes Windows CPU timer resolution #2525

nscaife opened this issue Apr 4, 2016 · 6 comments

Comments

@nscaife
Copy link

nscaife commented Apr 4, 2016

Client: 1.0.14 Service: 1.0.14

Microsoft Windows [Version 10.0.10586]

On Windows, the Keybase background utility requests an increased CPU timer resolution, even when idling. This can cause decreased battery life on mobile devices. From powercfg -energy:

capture

Is this intentional? It looks like the utility is idling in the background but keeps the request active.

@cjb
Copy link
Contributor

cjb commented Apr 4, 2016

CC @zanderz @taruti

@taruti
Copy link
Contributor

taruti commented Apr 4, 2016

This is probably golang/go#8687

@nscaife can you confirm what Runtime says in Platform information from keybase status?

This should be fixed in versions compiled with 1.6, but present in versions compiled with 1.5.x.

@nscaife
Copy link
Author

nscaife commented Apr 4, 2016

@taruti No problem, here's that output:

Platform Information:
    OS:        windows
    Runtime:   go1.5.3
    Arch:      386

@taruti
Copy link
Contributor

taruti commented Apr 4, 2016

Thank you.

This should go away when updating Keybase to a version built with Go version 1.6. (I'd wait 24h before updating for a build with #2522 fix included).

@zanderz
Copy link
Contributor

zanderz commented Apr 6, 2016

@nscaife
Copy link
Author

nscaife commented Apr 7, 2016

This looks like it is fixed now, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants