Closed astavs closed 10 years ago
Call graph:
6425 Thread1076716: Main Thread DispatchQueue
That's a known issue with the AddressBook/Contacts plugin. Sometimes it just catch itself in a hot loop doing something-we-can-only-deduce. I'd say it's related to iCloud syncing, because I don't remember seeing such usage spikes from that plugin in the old version, but I could be wrong.
Makes QS unusable for me (with the plugin enabled).
Do you have Contacts integrated with any external source, like Facebook or Exchange?
With iCloud and 1 LDAP account. No Facebook/Exchange/Gmail.
I'm also having this issue after updating this morning.
Can provide sample or more info if you let me know what you need.
I'm experiencing similar issues with QS for a week or so. I'm running Mountain Lion 10.8.4 and QS sometimes consumes up to 750% of CPU. I also experienced a problem where QS consumed 1,57 GB of RAM memory. Below are some screenshots from Activity Monitor. I also took samples, in case they are useful.
I checked the Contacts plugin and saw I am using version 2.1.4, which was released on august 13, so I'm not sure this is the problem, as my problems started a week ago or so. I have Contacts integrated with iCloud.
When this happens again, (the high CPU usage) can you click the "Muestrear proceso" and copy/paste the output to https://gist.github.com/ If you think it's a problem with the contacts plugin, could you try disabling it to see if the problem goes away?
On 29 Sep 2013, at 21:21, nach0 notifications@github.com wrote:
I'm experiencing similar issues with QS for a week or so. I'm running Mountain Lion 10.8.4 and QS sometimes consumes up to 750% of CPU. I also experienced a problem where QS consumed 1,57 GB of RAM memory. Below are some screenshots from Activity Monitor. I also took samples, in case they are useful.
I checked the Contacts plugin and saw I am using version 2.1.4, which was released on august 13, so I'm not sure this is the problem, as my problems started a week ago or so. I have Contacts integrated with iCloud.
— Reply to this email directly or view it on GitHub.
I just went to sample the process, but doesn't seem to be using the same 100% CPU today. Hopefully it's sorted itself out for me.
@pjrobertson I had already done that (sorry I didn't make myself clear in my previous comment). I have just uploaded three samples to gist corresponding to CPU usages of 694%, 756% and to RAM usage of 1,57 GB (not sure this one is related, but it happened recently for the first time, just like the CPU issues). They are available here: https://gist.github.com/nach0/6753143
I actually have no evidence to think that my issues are related to the Contacts plugin, I just read about a known issue with that plugin in a previous comment. I'm not sure I can test it by disabling the plugin because this problem is not constant, the high CPU usage has just happened twice in a week (and I use QS all the time in my mac, which I use a lot over the day). After forcing quit and relaunching the problem disappeared.
The last 2 samples were caused by #1453 so they shouldn't happen again after the next release. I'm still unsure about the first though. Looks like a missing autorelease pool somewhere (or maybe it's just a side-effect of the aforementioned issue).
Same issue on Mavericks. Issue completely resolved by disabling Contacts plugin.
I'm having this problem again now, even after updating to the latest version downloaded from the website.
Here's the trace... https://gist.github.com/ToGri/a9c350a2e591e1580b2d
I'm not sure how to disable the Contact plugin, as Quicksilver never loads far enough for me to access the settings & disable it now. Any advice on how I do this?
I haven't had any issues for the last 2 weeks, maybe the update fixed it for me.
@ToGri I'm no expert but I would suggest removing the Contacts plugin from ~/Library/Application Support/Quicksilver/PlugIns. Actually I believe it's the one named com.blacktree.Quicksilver.QSAddressBookPlugIn.179.qsplugin.
You could just move it to another folder in case you want to have a backup, however you can always redownload it, so I believe it's not necessary to backup the plugin.
All of @nach0’s suspicions are correct.
As for the actual fix @pjrobertson, should we maybe give out a test build based on #1497 to see if it makes a difference?
Just to update... followed @nach0 's advice & moved the QS AddressBook Plugin files to the 'disabled' folder & all is right with the world (or at least Quicksilver) for now.
Will we need to do anything then the update to the Address Book plugin is released?
Will we need to do anything then the update to the Address Book plugin is released?
You won’t see updates for plug-ins that you don’t have installed, so you won’t even know about it. But the problem might be with the app and not the plug-in. In any case, you should see an update here when something changes that we think fixes it.
OK. Thanks for the info. I'll try it again shortly.
This should be fixed by quicksilver/com.apple.AddressBook-qsplugin#8
I'm running QS on Mavericks and its consuming 100% of the CPU. I can send a sample of QS to whoever wants to take a look, github won't let me upload it here.