Problem with run on boot on a solid state disk

[dcnicholls]

My new MBP has the 512G solid state disk. If I set QS to start at
login, I find that the "QS" doesn't disappear from the desktop like it
used to. And there are other problems.

I think the problem may be caused by the speed of the solid state
drive boot. If I disable start at login in QS, then run it manually
after the system has booted, everything seems to work normally.

Sounds like some sort of timing thing. Can it be fixed?

DN

[Hugh Taylor]

I noticed the same problem on a new MacBook Air. Is one of your other problems that the search box will pop up, but you can't enter anything into it? I've also noticed that opening QS in different desktops brings up different a different history.

[dcnicholls]

Yes, I do see that. My only solution so far is to manually add QS to
the dock, uncheck "show in dock" and "run on login", the restart QS.
On next boot, QS does not run automatically but when run from the dock
icon, it works properly.

DN

[MooMadCow]

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'm using a Mac Pro with a SSD boot drive... so.. I'm guessing it's
the same issue with boot timing.

[Rob McBroom]

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/>

[Daniel]

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.

[MooMadCow]

Hrm... I would love to help, but I have NO idea how to build QS from
source or anything.

[MooMadCow]

This problem still comes up on random occasions with the latest build (B65).

QS would crash on launch when I first start the system. Then I will be presented with a dialog asking me to clear cache or do nothing. Either way QS will relaunch itself. Clearing cache seems to fix the problem for a little while, but after a few reboots the same thing happens again.

[Rob McBroom]

On Mar 20, 2012, at 3:59 PM, MooMadCow wrote:

> This problem still comes up on random occasions with the latest build (B65).
>
> QS would crash on launch when I first start the system. Then I will be presented with a dialog asking me to clear cache or do nothing. Either way QS will relaunch itself. Clearing cache seems to fix the problem for a little while, but after a few reboots the same thing happens again.

Is it crashing, or is it freezing (where the QS letters don’t quite disappear and you can’t type anything)? If it’s the former, do you have the Services Menu plug-in installed? It seems to have been crashing for a lot of people lately. If it’s the latter, try the B66 pre-release and see if it’s fixed.

[Oliver Schrenk]

I had a similar issue with b66 3922 (and before). After a reboot I couldn't access Quicksilver. When I then started it reported a crash and offered to clear the caches.

This error was reproducible. I found out that the Quicksilver process was running after a fresh reboot (I checked with `ps -ef | grep -i quicksilver` after opening Terminal the old fashioned way). Starting it manually again would produce the `Clear Caches` Dialog. I believe the Dialog is gone with b66 3923 now. But I still couldn't invoke Quicksilver after a reboot.

I found the culprit though. It was me!

The problem was that I checked the Box "Hide" in `Preferences > Accounts > <You> > Login Items` for Quicksilver! When unchecked I can access Quicksilver right from the start, even after a reboot.

[MooMadCow]

it is crashing on startup, and it doesn't do it every time, seems to be intermittent. The logo is not freezing, so not the same bug as the other thread. It is simply crashing, giving me a dialog to either "Do Nothing" or "Clear Cache" (I forgot what the third option was.. I think it was Quit?). I've tried both, either way QS would relaunch itself, and clearing cache doesn't seem to fix the issue.

I don't have the services menu plugin installed.

On B66 now, still the same thing.

[Rob McBroom]

On Mar 29, 2012, at 5:37 PM, MooMadCow wrote:

> it is crashing on startup, and it doesn't do it every time, seems to be intermittent.

Can you provide a crash log from ~/Library/Logs/DiagnosticReports?

[MooMadCow]

Today when I turned on my computer, the same thing happened again. I immediately tried looking for the crash log, but it doesn't even make a crash log entry of any sort for the boot crash... The only entries are from the night before when I turned off the computer:

4/2/12 11:26:31.029 PM com.apple.launchd.peruser.501: (com.apple.quicklook[16760]) Exited: Killed: 9

Then again, a lot of other processes are also being killed on shut down, not sure if it matters at all.

[MooMadCow]

Hrm.. I thought I replied to this a while ago.. apparently not. There are no logs from this crash at all, it seems.

On Friday, March 30, 2012 8:03:03 AM UTC-7, Rob McBroom wrote:

[MooMadCow]

So to post more updates in this thread... I have now 3 Mac with SSD's...

Mac Pro w/ Samsung SDD installed
Macbook Air w/ 128GB SSD
Macbook Air w/ 255GB SSD (work laptop)

All 3 exhibits the same problem with Quicksilver. Random on launch crashes, doesn't always occur. No crash logs on all 3 computers.

[Ian Hay]

this is odd, not that this helps fix it but I also have a Mac Pro & Air with SSD and do not have any issues like this, standard install, latest versions of QS on SL and Lion

-- You received this message because you are subscribed to the Google Groups Quicksilver group. To post to this group, send email to blacktree-...@googlegroups.com. To unsubscribe from this group, send email to blacktree-quicks...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/blacktree-quicksilver?hl=en

[Rob McBroom]

On May 9, 2012, at 6:43 PM, MooMadCow wrote:

So to post more updates in this thread... I have now 3 Mac with SSD's...

Mac Pro w/ Samsung SDD installed
Macbook Air w/ 128GB SSD
Macbook Air w/ 255GB SSD (work laptop)

All 3 exhibits the same problem with Quicksilver. Random on launch crashes, doesn't always occur. No crash logs on all 3 computers.

Is this when Quicksilver launches on login, or when Lion auto-resumes everything on login (or both)? There are differences. For instance, on my system, if I login fresh, everything pops right up. If Lion “reopens windows” for me, there’s a long delay (30+ seconds) before certain things (including Quicksilver) launch.

Since you don’t see any crash logs, is it possible that Quicksilver’s just not running yet?

[MooMadCow]

This is the default Lion shut down (which is auto-resume everything on start-up). However the behavior is inconsistent because sometimes it loads just fine, other times it doesn't. QS is also the only app that does this out of all the apps I've got launching on startup.

I also get a 30 second delay with some apps if they're left to resume. Namely, for some reason Firefox causes a "pause" on my system when loading apps on startup (it even stops loading of SteerMouse and other stuff). However, QS has also never crashed on startup with this "pause"... which leads me to think that load order or something is a problem. I've even tried the other methods of adding QS to login startup items without using the built-in preferences in QS to start up. Didn't make any difference to the peculiar behavior.

Also, when I leave the system to resume applications, out of all my apps only Firefox causes a "pause". Everything else loads super fast (SSD after all) and doesn't seem to have any trouble at all.

Only other thing I can think of is possibly conflict with other startup items like... Dropbox maybe? I don't know, something that would cause the index load to fail on startup if it's not loaded in some proper order?