-
Notifications
You must be signed in to change notification settings - Fork 76
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
(Performance/Power) Continuous activity when should be idle #208
Comments
I don't see a way to attach a file, so I'll paste the [unfortunately lengthy] sample here: Sampling process 170 for 3 seconds with 1 millisecond of run time between samples Date/Time: 2012-09-16 10:19:17.674 -0700 Call graph: |
It looks like something is happening in a timer that invalidates the window, but it's so quick that the sample doesn't catch it. |
I also have problems where I have GitX running and should be idle (on a different desktop!) and all of a sudden I hear my laptop's fans kick in. Activity Monitor shows the process using 115% cpu (I guess more than one CPU?). It program seems responsive, but the only way to stop it from using so much resources is to quit and restart. |
I've observed this a couple of times now. After GitX has been running for a while, at some point it idles up to about 15% CPU activity and stays at that level, even though I'm not actively using it. Quitting and restarting the program returns it to a quiet idle state.
I sampled and did a quick time profile and the activity appears to be window redraws triggered by timers calling into -[PBCommitMessageView drawRect:], but that's from a very quick examination without any knowledge of the code base. The only theory I have at present is that switching branches and doing commits, pushes, etc., from the command line while GitX is running somehow trigger this state.
The text was updated successfully, but these errors were encountered: