Repeated lockups with apparent sqlite access problem

[eejd]

Quicksilver has been consistently locking up, perhaps correlated with a recent MacOS X update, but while the cause is unknown the result is that when quicksilver is restarted it operates correctly for a period of time, then slows its response time, then eventually locks up (spinning disk on hover, not responding via activity monitor, etc). Sampling the process shows apparent sqllite access. I can provide an example sample of the process during a lockup.

Process: Quicksilver [620]
Path: /Applications/Utilities/Quicksilver.app/Contents/MacOS/Quicksilver
Load Address: 0x10d49f000
Identifier: com.blacktree.Quicksilver
Version: 1.1.3 (4007)
Code Type: X86-64
Parent Process: launchd [274]

Date/Time: 2014-03-10 09:57:19.604 +0000
OS Version: Mac OS X 10.9.2 (13C64)

[skurfer]

I don’t think we’re using SQLite anywhere in Quicksilver (directly), but some of the plug-ins use it via FMDB. Try disabling the Firefox and/or Chrome plug-ins temporarily to see if the problems go away.

[eejd]

I'll try that. I just tried to download and build QS to enable debugging and begin providing better feedback. However, I encountered two problems. First, the version built from master self-reports to be even older than the current release (i.e. QS_INFO_VERSION == 1.1.0). Second, after building both release and developer versions, I couldn't get even the basic trigger I use (^SPACE) to work.

I've reverted back to the production build from the DMG and have disabled the chrome plugin and will let you know what I observe. I do have a number of process samples I can send to someone when/if I figure out who it should go to. Apparently I cannot attach non image files in the issue tracker.

On 11 Mar, 2014, at 18:24 , Rob McBroom notifications@github.com wrote:

I don’t think we’re using SQLite anywhere in Quicksilver (directly), but some of the plug-ins use it via FMDB. Try disabling the Firefox and/or Chrome plug-ins temporarily to see if the problems go away.

—
Reply to this email directly or view it on GitHub.

[skurfer]

First, the version built from master self-reports to be even older than the current release (i.e. QS_INFO_VERSION == 1.1.0).

We had to do some unexpected hot-fixing on 1.1.x after some things were merged into master for 1.2.x. If you git checkout v1.1.x before building, you should get 1.1.3. Also, be sure to get the submodules with git submodule init; git submodule update.

Second, after building both release and developer versions, I couldn't get even the basic trigger I use (^SPACE) to work.

This is a common problem. Make sure you select the “Quicksilver Distribution” target before building. Otherwise, you’ll get just the application, but no plug-ins. See http://qsapp.com/wiki/Building_Quicksilver (though it needs some updating because it doesn’t mention the submodules).

I do have a number of process samples I can send to someone when/if I figure out who it should go to. Apparently I cannot attach non image files in the issue tracker.

Not by drag-n-drop, but pasting a URL should work. For textual stuff, some people just paste it all here or some people create a gist.

[pjrobertson]

This may well be fixed by the update to the Firefox plugin. If we are using sqlite3.c anywhere else in our code/plugins, then we should make sure to update it.

sqlite3 is now thread-safe and the code much more robust than before.