Closed cerberus1 closed 9 years ago
There’s not enough detail here to say, but this is probably fixed by #1970. A new release should be out soon.
Okay as long as you're on it I'm sticking with Quicksilver. I'm now using the previous build, recovered from the trash, and I will wait for the next update. I rely on the calculator module and the clipboard history, and the shelf. And I am very happy with this, although I keep hearing about this thing called Butler or Alfred. I just want to say that I've had an awesome experience with Quicksilver for at least the last five or six years, and it is free so thank you very much for developing it.
From: Rob McBroom Sent: Sunday, November 16, 2014 16:22 PM To: quicksilver/Quicksilver Cc: cerberus Subject: Re: [Quicksilver] Hang on 10.8.5 (#1989)
There’s not enough detail here to say, but this is probably fixed by #1970. A new release should be out soon.
— Reply to this email directly or view it on GitHub.
Hi Rob,
I've sampled the process when it is hung: I hope this is helpful…
Jeff
<><><><><><><><><><><><><><><><><><><><><><>
Sampling process 25423 for 3 seconds with 1 millisecond of run time between samples Sampling completed, processing symbols... Analysis of sampling Quicksilver (pid 25423) every 1 millisecond Process: Quicksilver [25423] Path: /Applications/Utilities/Quicksilver.app/Contents/MacOS/Quicksilver Load Address: 0x106cb0000 Identifier: com.blacktree.Quicksilver Version: 1.2.0 (400F) Code Type: X86-64 (Native) Parent Process: ??? [1]
Date/Time: 2014-11-19 14:16:17.338 -0500 OS Version: Mac OS X 10.8.5 (12F45) Report Version: 7
Call graph: 2746 Thread_4511879 DispatchQueue_1: com.apple.main-thread (serial)
Total number in stack (recursive counted multiple, when >=5): 9 psynch_mutexwait (in libsystem_kernel.dylib) + 0 [0x7fff8a356118] 9 _dispatch_call_block_and_release (in libdispatch.dylib) + 15 [0x7fff86ec2f01] 9 _dispatch_client_callout (in libdispatch.dylib) + 8 [0x7fff86ebf0b6] 9 _dispatch_worker_thread2 (in libdispatch.dylib) + 304 [0x7fff86ec01fa] 9 _pthread_wqthread (in libsystem_c.dylib) + 404 [0x7fff858bccdb] 9 pthread_mutex_lock (in libsystem_c.dylib) + 536 [0x7fff858bfdcd] 9 start_wqthread (in libsystem_c.dylib) + 13 [0x7fff858a7191] 8 __26-[QSObject(Icon) loadIcon]_block_invoke (in QSCore) + 42 [0x106dd5f8e] 7 _pthread_start (in libsystem_c.dylib) + 327 [0x7fff858ba772] 7 thread_start (in libsystem_c.dylib) + 13 [0x7fff858a71a1] 6 -[QSResourceManager imageNamed:inBundle:](in QSCore) + 69 [0x106dfb677] 5 psynch_cvwait (in libsystem_kernel.dylib) + 0 [0x7fff8a3560f0] 5 _pthread_cond_wait (in libsystem_c.dylib) + 869 [0x7fff858befb9]
Sort by top of stack, same collapsed (when >= 5): psynch_mutexwait (in libsystem_kernel.dylib) 24714 psynch_cvwait (in libsystem_kernel.dylib) 13730 kevent (in libsystem_kernel.dylib) 5492 __select (in libsystem_kernel.dylib) 2746 mach_msg_trap (in libsystem_kernel.dylib) 2746
Binary Images:
0x106cb0000 - 0x106ceeff7 +com.blacktree.Quicksilver (1.2.0 - 400F) <0661EE3E-19BD-3ABC-B37F-E347329D40B7> /Applications/Utilities/Quicksilver.app/Contents/MacOS/Quicksilver
0x106d0f000 - 0x106d64fff +com.blacktree.QSFoundation (??? - 2.0)
Yes, that’s definitely the same thing described in #1957. I’ll try to get the new release out in the next day or so.
I was prompted to update yesterday, but QS hangs now whenever i try to use it. I've reverted to the "nov 5, 2013" version", which still works.
Jeff Dinces