AHH.. the Luxury of !=Doze "Computing"

Post #372,315 by Ashton 3/8/13 4:44:08 PM Reply	AHH.. the Luxury of !=Doze "Computing" iMac [Hypatia by name] had become 'sluggish' over recent many days: even kb repeat occasionally slowed to crawl. Had not closed/opened Safari for those many days: my usual 100 +/- windows open, in Dock. Was time for sleuthing, closing/opening things--maybe reboot if my deductive powers ran out of guesses. Wanted first to finish a flic on Einstein VS A-Bomb. Then, abruptly: everything got Better [to use the technical term] Â Magic! OK, time to see what Fixed-itself: some data below (Had not perused any logs, for some weeks--usually I do look ~ 1/week.) So: surprised to note TWO "iMac Crashes" under DIAGNOSTIC AND USAGE INFORMATION These crashes had occurred while I was watching the You Tube flic! but nary a glitch occurred to my eyeballs.. No useless Error Message boxes.. No trips to the petabytes of ~~Windows Knowledge Base~~ Gigundo Bug Lists We Already Know About and the repeated gnashing of teeth which are (independently) on --> a Mission to Bite Ballmer on the Ass.. "Goodnight Gracie" graces the ends of some auto-launched remedies (maybe not those relevant here) eg. OS X banters<-with->Self! IT'S ALIVE! / Love It! this self-appendectomy-administering entity which also supplies requisite morphine, lest the user feel inconvenienced. (But we have to Help, at least: closed, weeded, decided to reboot anyway: came back with ~ 93% cpu Free--with 100 URLs open. And I didn't have to use even the cache-emptying Util or other such enterprises iStat==indispensable; time to send them some $$: you'unses too? Herewith excerpts from Data-land; guess WebKit-anything, is Safari-only: So then: what is EXC_BAD_ACCESS (SIGSEGV) ?? ****************************************************************************** "Web Process" Report: Process: WebProcess [14202] Path: /System/Library/PrivateFrameworks/WebKit2.framework/WebProcess.app/Contents/MacOS/WebProcess Identifier: com.apple.WebProcess Version: 6534.57 (6534.57.2) Build Info: WebKit2-75345702~2 Code Type: X86-64 (Native) Parent Process: Safari [14200] Date/Time: 2013-03-07 23:44:35.901 -0800 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: 0x000000000000000d, 0x0000000000000000 Crashed Thread: 8 Thread 0: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x00007fff8684ca6a __semwait_signal + 10 1 libSystem.B.dylib 0x00007fff8684c8f9 nanosleep + 148 2 com.apple.JavaScriptCore 0x00007fff88fd803c WTF::fastFree(void) + 2028 3 com.apple.WebCore 0x00007fff8056cac8 WebCore::CachedScript::destroyDecodedData() + 200 4 com.apple.WebCore 0x00007fff80fff90b WebCore::MemoryCache::pruneLiveResourcesToSize(unsigned int) + 123 5 com.apple.WebCore *********************************************************************** "Console" Report: Process: Console [23704] Path: /Applications/Utilities/Console.app/Contents/MacOS/Console Identifier: com.apple.Console Version: 10.6.3 (224) Build Info: ConsoleX-2240000~9 Code Type: X86-64 (Native) Parent Process: launchd [104] Date/Time: 2013-03-08 01:53:21.094 -0800 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Interval Since Last Report: 8177216 sec Crashes Since Last Report: 5 Per-App Interval Since Last Report: 88225 sec Per-App Crashes Since Last Report: 1 Anonymous UUID: 1F501E23-46B3-4377-8150-1803BECB45C6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000001e Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: objc_msgSend() selector name: outlineView:objectValueForTableColumn:byItem: Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff86692f0c objc_msgSend + 40 1 com.apple.AppKit 0x00007fff83252a7c -[NSTableView preparedCellAtColumn:row:] + 323 2 com.apple.AppKit 0x00007fff8326b963 -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 47 3 com.apple.AppKit 0x00007fff8326b8d9 -[NSOutlineView _drawContentsAtRow:column:withCellFrame:] + 95 4 com.apple.AppKit 0x00007fff8326a9fc -[NSTableView drawRow:clipRect:] + 1242 5 com.apple.AppKit 0x00007fff8326a2ef -[NSTableView drawRowIndexes:clipRect:] + 369 6 com.apple.AppKit 0x00007fff8326a170 -[NSOutlineView drawRowIndexes:clipRect:] + 131 7 com.apple.AppKit 0x00007fff83268c9c -[NSTableView drawRect:] + 1302 8 com.apple.AppKit 0x00007fff8325ed75 -[NSView _drawRect:clip:] + 3566 9 com.apple.AppKit 0x00007fff8325c54b -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 2112 10 com.apple.AppKit 0x00007fff8325ced6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4555 11 com.apple.AppKit 0x00007fff8325ced6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4555 12 com.apple.AppKit 0x00007fff8325ced6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4555 13 com.apple.AppKit 0x00007fff8325ced6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4555 14 com.apple.AppKit 0x00007fff8325ced6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4555 15 com.apple.AppKit 0x00007fff8325bb2c -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 254 16 com.apple.AppKit 0x00007fff832583de -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2683 17 com.apple.AppKit 0x00007fff831d1c0e -[NSView displayIfNeeded] + 969 18 com.apple.Foundation 0x00007fff85d17351 __NSFirePerformWithOrder + 384 19 com.apple.CoreFoundation 0x00007fff8208ab07 __CFRunLoopDoObservers + 519 20 com.apple.CoreFoundation 0x00007fff82066434 __CFRunLoopRun + 468 21 com.apple.CoreFoundation 0x00007fff82065d8f CFRunLoopRunSpecific + 575 22 com.apple.HIToolbox 0x00007fff843c47ee RunCurrentEventLoopInMode + 333 23 com.apple.HIToolbox 0x00007fff843c4551 ReceiveNextEventCommon + 148 24 com.apple.HIToolbox 0x00007fff843c44ac BlockUntilNextEventMatchingListInMode + 59 25 com.apple.AppKit 0x00007fff831a1eb2 _DPSNextEvent + 708 26 com.apple.AppKit 0x00007fff831a1801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 27 com.apple.AppKit 0x00007fff8316768f -[NSApplication run] + 395 28 com.apple.AppKit 0x00007fff831603b0 NSApplicationMain + 364 29 com.apple.Console 0x00000001000017a0 0x100000000 + 6048 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x00007fff8682ac0a kevent + 10 1 libSystem.B.dylib 0x00007fff8682cadd _dispatch_mgr_invoke + 154 2 libSystem.B.dylib 0x00007fff8682c7b4 _dispatch_queue_invoke + 185 3 libSystem.B.dylib 0x00007fff8682c2de _dispatch_worker_thread2 + 252 4 libSystem.B.dylib 0x00007fff8682bc08 _pthread_wqthread + 353 5 libSystem.B.dylib 0x00007fff8682baa5 start_wqthread + 13 ***********************************************************************************
Post #372,319 by crazy 3/8/13 6:14:14 PM Reply	Segment violation When a program is allocated memory in the computer, it is allocated in segments. These segments are put in a list as being used by your program. Every memory access by every program is tested against this list for ownership. If your program attempts to access memory it does not own, the operating system sends it the segmentation violation signal, which in turn will cause it to dump a core file (current memory image) for debugging and then KILL the program. Programs attempt bad memory accesses via buffer overflow bugs or bad pointer handling. You can also see this message pop up if your memory or your motherboard is going bad.
Post #372,920 by Ashton 3/25/13 5:04:16 PM Reply	Thanks, belated: got that from log after a bit No 'causality' in a thread fail ... ever seems to be decipherable; I vote--errant BIG Cosmic Ray, maybe a TeV-gamma in energy?
Post #372,931 by crazy 3/25/13 6:54:50 PM Reply	If you find yourself getting them during heavy use ie: watching video, pay attention to temperature. If you run multiple videos in multiple windows you can probably drive it up and trigger the error. Put a fan next to cpu (external to box, simply add airflow around it)(if possible, not paying attention of this is a laptop).
Post #372,933 by Another Scott 3/25/13 7:24:01 PM Reply	Good advice. A year or so ago I inherited a Dell E6400 laptop at work. It's a decent machine. I run 2 external monitors off it in a docking station while at work. When my office gets warm, it often throttled down and became a turtle - driving the external monitors is too much for the video chip while it's also working hard on other things. I blew out the dust and got a cooling pad thingy for it (CoolerMaster NotePal U3 - http://www.amazon.co...oduct/B003ZMF27G/ ) and haven't had the problem recur (will have to see how it does this summer before declaring the problem 'fixed'.) IIRC, Ashton's iMac had some problematic video issues for a while. More cooling may help quite a bit, but cooling an iMac probably isn't easy. Cheers, Scott.
Post #372,941 by Ashton 3/25/13 8:51:23 PM Reply	Thanks for tips, both.. Re temp: Fortunately there is: smcFanControl, which I installed days after acquisition of the iMAc. And I always attend to Temp--in any electronics--I have WInter/Summer values for the little fans. iStat gives me The Word every time I look, esp. at GPU, often warmer than CPU. (Once plugged in an ext. mon. It worked, but I don't use, so removed) Not related to-- As to that video glitch thing--I upped a couple fans (none is video-card specific) a few hundred rpm; last event was ~October IIRC. No plans to r&r that card after first securing New Tape and other watchmaker fiddles to disembowel the world's largest laptop. Not soon anyway, I hope. This machine has been nothing but a treat, after the progression from PDP-8 --> Osborne1/Otrona --> and all the Beastware greasy-kid stuff + the daily, Will-It-Work? If it dies irremediably next year, will just look for another 2yo and move from 20"-->21.5" BIG-screen!! (People who never owned Beastware before getting an Apple.. just Can't appreciate their Apple properly, I wot.)
Post #372,948 by crazy 3/26/13 7:12:12 AM Reply	Good quote and concept but You've been there since PDP, a bit different perspective. My PWW thought I was nutz for taking a new laptop, reformatting it, tossing win 8, installed Win 7 and required apps, and handed it to the wife for school work. He thought I gave it a lobotomy by "downgrading" it. I tracked down "In the beginning there was the command line", threw it on the projector screen, and told him to read it. THAT's 60 pages or so, I'm not reading that! FU, you are are reading the 1st couple of pages so you have a clue of what an OS is, and then we can have the discussion. 5 pages later he had a good start, and I emailed it to him to read the rest in his room. I'll quiz him. He started with Win, is a minor gamer, and does minor windows bitching but it is his world.

Welcome to IWETHEY!