quicksilver / Quicksilver

Quicksilver Project Source
http://qsapp.com
Apache License 2.0
2.73k stars 285 forks source link

Sierra hang #2282

Closed danielcompton closed 2 years ago

danielcompton commented 8 years ago

After updating my MacBook to Sierra, I got a new hang that I don't think I've seen before:

Date/Time:       2016-10-17 20:19:06 +1300
OS Version:      Mac OS X 10.12 (Build 16A323)
Architecture:    x86_64
Report Version:  25

Data Source:     Stackshots

Command:         Quicksilver
Path:            /Applications/Quicksilver.app/Contents/MacOS/Quicksilver
Version:         1.4.2 (401A)
Parent:          launchd [1]
PID:             1410

Event:           hang
Duration:        0.99s (process was unresponsive for 13107 seconds before sampling)
Steps:           10 (100ms sampling interval)

Hardware model:  MacBookPro9,2
Active cpus:     4

Fan speed:       1997 rpm

--------------------------------------------------
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
--------------------------------------------------

Heaviest stack for the main thread of the target process:
  10  start + 1 (libdyld.dylib + 21077) [0x7fffcf491255]
  10  NSApplicationMain + 1237 (AppKit + 27274) [0x7fffb8015a8a]
  10  -[NSApplication run] + 926 (AppKit + 245693) [0x7fffb804afbd]
  10  -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637 (AppKit + 7698667) [0x7fffb87668eb]
  10  _DPSNextEvent + 1093 (AppKit + 292341) [0x7fffb80565f5]
  10  _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 199638) [0x7fffb995fbd6]
  10  ReceiveNextEventCommon + 432 (HIToolbox + 200097) [0x7fffb995fda1]
  10  RunCurrentEventLoopInMode + 240 (HIToolbox + 200556) [0x7fffb995ff6c]
  10  CFRunLoopRunSpecific + 420 (CoreFoundation + 542836) [0x7fffba3bf874]
  10  __CFRunLoopRun + 1894 (CoreFoundation + 545334) [0x7fffba3c0236]
  10  __CFRunLoopDoBlocks + 356 (CoreFoundation + 546548) [0x7fffba3c06f4]
  10  __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 (CoreFoundation + 672716) [0x7fffba3df3cc]
  10  ___LSScheduleNotificationFunction_block_invoke_2 + 51 (LaunchServices + 104213) [0x7fffbb58f715]
  10  HIToolboxLSNotificationCallbackAllASNsFunc + 571 (HIToolbox + 631870) [0x7fffb99c943e]
  10  SendEventToEventTargetWithOptions + 43 (HIToolbox + 33167) [0x7fffb993718f]
  10  SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 428 (HIToolbox + 33606) [0x7fffb9937346]
  10  DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1708 (HIToolbox + 37077) [0x7fffb99380d5]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 242331) [0x10c6f429b]
  10  -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 (Foundation + 28899) [0x7fffbbdc00e3]
  10  _CFXNotificationPost + 667 (CoreFoundation + 358939) [0x7fffba392a1b]
  10  -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 2018 (CoreFoundation + 363058) [0x7fffba393a32]
  10  ___CFXNotificationPost_block_invoke + 50 (CoreFoundation + 631570) [0x7fffba3d5312]
  10  _CFXRegistrationPost + 427 (CoreFoundation + 632235) [0x7fffba3d55ab]
  10  __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 (CoreFoundation + 632492) [0x7fffba3d56ac]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 245383) [0x10c6f4e87]
  10  -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] + 118 (Foundation + 75062) [0x7fffbbdcb536]
  10  NSKeyValueDidChange + 486 (Foundation + 276052) [0x7fffbbdfc654]
  10  NSKeyValueNotifyObserver + 350 (Foundation + 277949) [0x7fffbbdfcdbd]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 253412) [0x10c6f6de4]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 253506) [0x10c6f6e42]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 191435) [0x10c6e7bcb]
  10  -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 (Foundation + 28899) [0x7fffbbdc00e3]
  10  _CFXNotificationPost + 667 (CoreFoundation + 358939) [0x7fffba392a1b]
  10  -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 2018 (CoreFoundation + 363058) [0x7fffba393a32]
  10  ___CFXNotificationPost_block_invoke + 50 (CoreFoundation + 631570) [0x7fffba3d5312]
  10  _CFXRegistrationPost + 427 (CoreFoundation + 632235) [0x7fffba3d55ab]
  10  __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 (CoreFoundation + 632492) [0x7fffba3d56ac]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 77218) [0x10c6cbda2]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 27801) [0x10c6bfc99]
  10  ??? (<B49A61DD-1113-3ED1-A23C-B9FADC304D9A> + 26207) [0x10c6bf65f]
  10  _dispatch_barrier_sync_f_slow + 402 (libdispatch.dylib + 54762) [0x7fffcf4665ea]
  10  _dispatch_thread_event_wait_slow + 85 (libdispatch.dylib + 109678) [0x7fffcf473c6e]
  10  __ulock_wait + 10 (libsystem_kernel.dylib + 107446) [0x7fffcf5c03b6]
 *10  hndl_unix_scall64 + 22 (kernel + 696134) [0xffffff80002a9f46]
 *10  unix_syscall64 + 582 (kernel + 6464358) [0xffffff800082a366]
 *10  ulock_wait + 993 (kernel + 5944129) [0xffffff80007ab341]
 *10  thread_block_reason + 222 (kernel + 1111278) [0xffffff800030f4ee]
 *10  ??? (kernel + 1115851) [0xffffff80003106cb]
 *10  machine_switch_context + 206 (kernel + 2118942) [0xffffff800040551e]

Process:         Quicksilver [1410]
Path:            /Applications/Quicksilver.app/Contents/MacOS/Quicksilver
Architecture:    x86_64
Parent:          launchd [1]
UID:             503
Task size:       171 MB
CPU Time:        <0.001
Note:            Unresponsive for 13107 seconds before sampling
Note:            3 idle work queue threads omitted

Full details at https://gist.github.com/danielcompton/fbf8177775bc886fa1c832eae86f721e

joho commented 8 years ago

I'm not sure if my problems are related but I've been having a lot of latency issues triggering quicksilver since my Sierra upgrade, sometimes a few seconds before it will come up. This morning I noticed quicksilver up there with Chrome in my battery usage too.

joelbrock commented 7 years ago

Maybe related as well: i'm having similar lagginess / crashiness but on El Capitan 10.11.8, with QS 1.4.2 (401A).

Symptoms: On startup i can trigger QS once. On subsequent trigger QS no longer responds. Maybe 2 to 3 minutes later the pane pops up. At other times the pane never pops up and i can see in Activity Monitor that QS is Not Responding and must be force quit. So essentially unusable.

I can't say for sure WHEN this began, it's been a while though. Perhaps since upping to OS X 10.11.

Not too much in Console.app to indicate what's happening:

12/13/16 9:37:16.091 AM Quicksilver[14604]: Unknown error calling sqlite3_step (11: database disk image is malformed) rs
12/13/16 10:03:40.272 AM Quicksilver[14604]: assertion failed: 15G1108: libxpc.dylib + 78286 [54D1328E-054E-3DAA-89E2-375722F9D18F]: 0x87
skurfer commented 7 years ago

The gist indicates that there’s something related to disk mounting going on. Do you have any Event Triggers for “Disk Mounted” or “Disk Ejected”? Is QS indexing anything on an external drive?

tiennou commented 7 years ago

This is a weird gist actually. The Binary Image section makes me think we're not even fully started, but maybe that's a red herring... Also, would be nice to know what B49A61DD-1113-3ED1-A23C-B9FADC304D9A refers to, in case that's not our code...

skurfer commented 7 years ago

This is for 1.4.2:

% dwarfdump --uuid Quicksilver.app/Contents/MacOS/Quicksilver
UUID: 8E3D64D5-EA74-306B-8DD7-ECEBC6E10DFE (x86_64) Quicksilver.app/Contents/MacOS/Quicksilver

Each plug-in has its own binary of course, but none of them are loaded. That is weird.

tiennou commented 7 years ago

find ~/Library/Application\ Support/Quicksilver/PlugIns -type f -perm +111 -print -exec dwarfdump --uuid {} 2&>1 \; | grep B49A61DD-1113-3ED1-A23C-B9FADC304D9A ?

This gives me no results here (caveat, I'm still on 10.11). Maybe try against /Applications ?

skurfer commented 7 years ago

Give this test build a try and let me know if it’s any better. The version should show as “1.5.2:mine”.

https://cl.ly/420r2R0z3R3d

pjrobertson commented 2 years ago

@danielcompton - we haven't heard back from you in a while, so we're going to close this. Hopefully the latest build fixed this for you!