The latest crash: Process: Quicksilver [402] Path: /Applications/Quicksilver.app/Contents/MacOS/ Quicksilver Identifier: com.blacktree.Quicksilver Version: ß61 (3900) Code Type: X86 (Native) Parent Process: launchd [342]
Date/Time: 2011-10-24 22:32:26.647 +0200 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000002a2a0000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: objc_msgSend() selector name: release Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x99195f9c objc_msgSend + 44 1 com.apple.AppKit 0x97a7ec63 -[NSButtonCell dealloc] + 359 2 com.blacktree.QSInterface 0x0010d2de -[QSObjectCell dealloc] + 75 3 com.apple.CoreFoundation 0x95907bcd _CFAutoreleasePoolPop + 253 4 com.apple.Foundation 0x976b5976 NSPopAutoreleasePool + 76 5 com.apple.Foundation 0x976b589e -[NSAutoreleasePool drain] + 130 6 com.apple.Foundation 0x976fcfea _NSAppleEventManagerGenericHandler + 274 7 com.apple.AE 0x9662cf5c aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166 8 com.apple.AE 0x9662ce5b dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43 9 com.apple.AE 0x9662cd65 aeProcessAppleEvent + 197 10 com.apple.HIToolbox 0x9521c197 AEProcessAppleEvent + 50 11 com.apple.AppKit 0x9796c7d2 _DPSNextEvent + 1420 12 com.apple.AppKit 0x9796bdd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 13 com.apple.AppKit 0x9792e1f3 -[NSApplication run] + 821 14 com.apple.AppKit 0x97926289 NSApplicationMain + 574 15 com.blacktree.Quicksilver 0x00002b59 0x1000 + 7001 On Oct 24, 6:21 pm, Henning Jungkurth <[email protected]> wrote: > A log of the crash should already be there in > ~/Library/Logs/DiagnosticReports/Quicksilver... > Pick the latest and send it to the list. Maybe We can figure out what > went wrong. > > Also check outhttp://qsapp.com/wiki/FAQ#Quicksilver_crashes > andhttp://qsapp.com/wiki/FAQ#Clearing_the_cache > and try if any of that helps. > > > > > > > > On Mon, Oct 24, 2011 at 6:15 PM, Sebastian Szwarc <[email protected]> > wrote: > > Ok my QS started to crash after some configuration attempt. > > now I cannot launch it. > > What to do to test a problem and create log? > > > On Oct 24, 4:38 pm, Patrick Robertson <[email protected]> > > wrote: > >> I do not believe ß61 has any issues with the Chat Support module. You can > >> try deleting it from ~/Library/Application Support/Quicksilver/PlugIns. > > >> If this does not work (and you've tried deleting the caches in > >> ~/Library/Caches/Quicksilver) the can you please send the log > >> at /Users/florentj/Library/Logs/ > >> DiagnosticReports/Quicksilver_2011-10-24-102615_LM-CT-953914.crash over to > >> us. > > >> Thanks, > > >> On 24 October 2011 15:31, jflo <[email protected]> wrote: > > >> > So does mine. Console logs look like it tries twice to load Chat > >> > Support and then segfaults. > > >> > 10/24/11 10:26:13 AM Quicksilver[18018] Prevented load of > >> > unidentified > >> > action from bundle Chat Support.qsplugin because the action's > >> > featureLevel (set from its Info.plist) is higher than NSApp's current > >> > featureLevel. This is not neccessarily an error. Sometimes this > >> > mechanism is used to prevent unstable actions from loading. > >> > 10/24/11 10:26:13 AM Quicksilver[18018] Prevented load of > >> > unidentified > >> > action from bundle Chat Support.qsplugin because the action's > >> > featureLevel (set from its Info.plist) is higher than NSApp's current > >> > featureLevel. This is not neccessarily an error. Sometimes this > >> > mechanism is used to prevent unstable actions from loading. > >> > 10/24/11 10:26:15 AM com.apple.launchd.peruser.502[593] > >> > ([0x0-0x1865864].com.blacktree.Quicksilver[18018]) Job appears to have > >> > crashed: Segmentation fault > >> > 10/24/11 10:26:15 AM ReportCrash[18020] Saved crash report for > >> > Quicksilver[18018] version ß61 (3900) to /Users/florentj/Library/Logs/ > >> > DiagnosticReports/Quicksilver_2011-10-24-102615_LM-CT-953914.crash > > >> > Any known workarounds? Can I disable Chat Suport from a plist > >> > somewhere or anything? > > >> > On Oct 23, 5:21 pm, Sebastian Szwarc <[email protected]> wrote: > >> > > Unfortunately it crashes on my Snow Leopard after run....:(((( > > >> > > Sebastian
