crash message when using the restart shortcut (cmd+ctrl+q)

[jeanravin]

Well… everything is in the title. The app correctly relaunch though.

(ß63+10.6.8)

[pjrobertson]

Is this a problem with the new crash dialogue in ß63?

What happens if you quit Quicksilver (using ⌘Q) then launching it normally?

I cannot reproduce this, unfortuantely.

On 22 November 2011 12:57, jeanravin <
reply@reply.github.com

wrote:

Well… everything is in the title. The app correctly relaunch though.

---

Reply to this email directly or view it on GitHub:
#587

[jeanravin]

It happens since ß63.

I've tried to clear caches without result.

⌘Q + relaunch works correctly

[philostein]

Confirmed. New to ß63 for me. Also for @Commandor on Twitter. 10.6.8. Normal quitting is fine.

[pjrobertson]

Perhaps it's a 10.6 thing?

@HenningJ - can you try and reproduce? Maybe applicationWillTerminate isn't
being called when you relaunch with
⌘⌃Q on SL

On 22 November 2011 13:30, philostein <
reply@reply.github.com

wrote:

Confirmed. New to ß63 for me. Also for @Commandor on Twitter. 10.6.8.
Normal quitting is fine.

---

Reply to this email directly or view it on GitHub:
#587 (comment)

[Commandor]

I am on 10.7.2, not 10.6.

2011/11/22 Patrick Robertson
reply@reply.github.com:

Perhaps it's a 10.6 thing?

@HenningJ - can you try and reproduce? Maybe applicationWillTerminate isn't
being called when you relaunch with
⌘⌃Q on SL

On 22 November 2011 13:30, philostein <
reply@reply.github.com

wrote:

Confirmed. New to ß63 for me. Also for @Commandor on Twitter. 10.6.8.
Normal quitting is fine.

---

Reply to this email directly or view it on GitHub:
#587 (comment)

---

Reply to this email directly or view it on GitHub:
#587 (comment)

[Commandor]

I am on 10.7.2, also crash when relaunching with ctrl+cmd+q.

[HenningJ]

Yeah, I'm getting that too.
I might even know why. @pjrobertson I think this might be caused by the recent fix in pull request #585. It will relaunch before the old app has actually quit, so the new one will read the state file, before the old one has written that it quit successfully. Maybe? :-)

[philostein]

That makes sense - saw the dialog before the bezel disappeared… :)

[Sesquipedalian]

More details at issue #604. (Sorry for duplicate listing this bug; I didn't notice this issue report until afterwards.)

[clarkewd]

Maybe it's just me but it but my experience with Quicksilver is that sometimes it just crashes. Sometimes that is when it is first launching, and sometimes it's when I try and add an advanced custom trigger, or perhaps if I try and use some of the proxies and they don't like the object in the first pane. But the bottom line is I don't really care if it crashes because it's so awesome (after it actually starts).

And so when it crashes I immediately start trying to relaunch it until it gets going agin. Sometimes that's one time and sometimes it's about 5 times - but again I don't really care what is wrong with QS that much and I know you guys are working to make it better, so I'm not going to complain or ask "can you please make it immune to crashing" - that seems a little unreasonable.

But what I would ask is can we please just make it easier to relaunch it when it crashes? The crash reporting tool is a step in the right direction, but I feel like it might be good if it had an option that said something like "Always just try and restart Quicksilver X number of times before showing the crash dialog"

[Sesquipedalian]

You've gone a bit off-topic there, clarkewd. But I think you may find something like what you are looking for at https://groups.google.com/group/blacktree-quicksilver/msg/c9def098f6c12cbe?hl=en

[clarkewd]

Haha, so it seems I have. I ended up here after looking at issue 587 (sort of a duplicate). I should have prefaced my soapboxing by mentioning that I'm annoyed by the popup message that keeps showing up and really I just want to be able to seamlessly restart quicksilver - even if it crashes when doing so. Thanks. BTW that is a really wonderful tip you have there with the KeepAlive setup :)

[pjrobertson]

This issue was fixed in ß64

[Orion751]

All looks well in ß66.