Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system Subject: Re: Major Crashing! Date: 13 Oct 2016 00:11:57 GMT Organization: People for the Ethical Treatment of Pirates Lines: 70 Message-ID: References: <2016100914440485222-xxx@yyyzzz> <2016100916560594420-xxx@yyyzzz> <2016101017422133874-xxx@yyyzzz> <2016101022221792062-xxx@yyyzzz> <2016101107573659384-xxx@yyyzzz> <2016101109410119907-xxx@yyyzzz> <2016101111142593545-xxx@yyyzzz> <2016101123245356806-xxx@yyyzzz> <2016101211123866191-xxx@yyyzzz> X-Trace: individual.net wE598glhEtHU7f/45AT7KguUzZmbo2CpkHT4aEQP/IZS85BUu9 Cancel-Lock: sha1:VgI7v3lAkETS8B/M/tBiqa+7Gnw= Mail-Copies-To: nobody User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:95559 On 2016-10-12, gtr wrote: > Okay, got off easy yesterday with none. > > Today I got bit at around 10:37 a.m. It would be helpful to know: What were you doing when you first noticed the problem? What apps were you running at the time? How busy was the CPU? Which apps were using the most CPU at the time? You can find details about these in /Applications/Utilities/Activity Monitor. If the hangs happen frequently, you can just leave it running in preparation. > This, followed by a clown-car of activity. Do you mean that actions you took (clicks, typing) while the hang was happening finally got processed in short succession once the hang was over? That's what it sounds like, but it's hard to tell by your wording. > While it remained locked I fetched a USB keyboard which took a few > minutes, plugged it in, found it too would not work. Then rebooted, > remembered I was advised to try a nvram reset, so once up, I tried to > restart and reboot anew. So you rebooted *twice* after the initial hang? > Inexplicable problems with programs that wouldn't quit, had to be > force-quit and then a beachball refusing activit of all kind it took > another two minutes or more before I could reboot. Are you saying the above happened *after* you had rebooted once or twice? > The sys.log [below for ease of reading notes] has nothing at 10:37, > but has plenty relating to GoogleSoftwareUpdateAgent, and many more > like it relating to GoogleSoftwareUpdate. Some questions: Which Google software packages do you have installed on this computer? Which of those apps were running at the time of the hang? > Little Snitch disallows any outgoing callas to Google Software Update > and to GoogleSoftwareUpdateDaemon. That would mean each time GoogleSoftwareUpdate attempts to connect to Google, the connection will sit and spin and eventually time out, potentially causing problems with related Google apps. Have you considered disabling (removing) GoogleSoftwareUpdate from the system?: > Which reminds me of a question. Why does seemingly 90% of my programs > want to chat with google-analytics, and can't I refuse them all > without issue? Which programs, specifically? -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR