I realize I've mostly just been ignoring the problem, but I have something that sounds similar, and I've actually recently successfully compiled QS from source to make a change to the Bezel interface. I'm also vaguely familiar with git. Maybe I can help—although I won't be able to for a little while, since my life is kinda hectic right now. Maybe in a couple weeks?
So, here's my problem: Back in the B54 days, or maybe the B55-59 days, pre-qsapp.com, QS crashed a lot, and I'm so reliant on it I would always have to stop and think to get it back open (since I normally only open apps with QS). So I made a launchd entry for it so it gets restarted automatically if it crashes. It actually crashes several times a day, but I don't really care since I'm never without it for long. Specifically, though, it almost always crashes at boot—sometimes multiple times. Unlike the OP, though, I'd guess it has to do with machine _slowness_ at boot. I don't have an SSD, have an older machine, and I have a lot of login items, so it takes my computer several minutes to go from desktop picture to functional system. During this time QS often crashes multiple times. (Less so now, since it doesn't try to restart until I answer the dialog, so usually it crashes once and when I sit down to use the machine I click "do nothing" and go on—although if the machine is at all still sluggish at that point, QS often crashes again.) It also crashes sometimes during the day if the machine is under heavy load and I try to invoke QS and type really fast, at which point it usually crashes once or twice more when it restarts before stabilizing. ...I'm realizing that this is probably more than just what the OP has a problem with, so I may not be a good candidate for testing. On Dec 18, 9:27 am, Rob McBroom <[email protected]> wrote: > On Dec 17, 2011, at 8:37 PM, MooMadCow wrote: > > > I'm having the same problem with QS crashing on boot. This seems to > > exhibit itself with B62 and B63... but not B61. I've reverted back to > > B61 temporarily so I don't keep on seeing the "Quicksilver has > > crashed" dialogue on boot. > > I’ll post the same thing here and on GitHub: > > Is there anyone having this issue that thinks they could build Quicksilver > from source? If so, we could have you run `git bisect` to pinpoint the > problem. (I’d provide instructions. It’s not too scary.) > > A remote desktop session is also an option, but since this involves > restarting to test, that’s not practical. > > -- > Rob McBroom > <http://www.skurfer.com/>
