VERY Strange occurrance. Not quite a catastrophe.

Question

Level 7

20,924 points

VERY Strange occurrance. Not quite a catastrophe.

Greetings

This more of a report than a question or problem, as I don't anticipate a repeat. I cannot replicate it.

Short version... Went to About this Mac under the Apple menu, clicked More Info... to open System Profiler, clicked Power in the TOC under Hardware. After about 10 seconds --- WHAM !

Blue screen
Cursor came back after about 10 seconds
Login dialog appeared as if System restart had occurred, but none of the normal processes of a restart.
Logged in
All apps opened as if "recovered" from a crash

I have been using Macs since Mac SE30 and have never seen anything like this.

For what its worth,

-- PowerBook PPC G3/500 FireWire (Pismo), 512Mb SDRAM, PCI: TXN,PCI1211-00:No Card, Mac OS X 10.4.11 (8S165) - Kernel version:Darwin 8.11.0, TOSHIBA MK4026GAX 40GB internal drive, MATSHITADVD-ROM SR-8174, LaCie 1394 Disk drive LUN 0 SBP-LUN: 40GB FireWire drive, Browser: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28

Anyone ever seen this misbehavior? Especially from a native app like System Profiler?

Congrats to Germany, World Cup Champs 2014

CCC

Posted on Jul 13, 2014 3:01 PM

Reply

Answer 1

Best reply

BDAqua

Level 10

239,225 points

Jul 13, 2014 3:31 PM in response to ChitlinsCC

I don't believe I've ever seen it. 🙂

Reply

Answer 2

K Shaffer

Level 7

34,978 points

Sep 24, 2015 10:47 AM in response to ChitlinsCC

Does the Console utility want to let you follow a trail of systemic bread crumbs

to see if there may be a cause and effect, or at least some indication of what

may have occurred? Doubtful it would be so helpful as to suggest anything, tho!

Sounds like your 'ghost in the machine' is needing

a transfusion of something more from elsewhere... 🙂

Reply

Answer 3

ChitlinsCC Author

Level 7

20,924 points

Jul 14, 2014 6:38 AM in response to K Shaffer

Snicker...

Console certainly shows the System Profiler had a series of errors... don't know what ANY of it means (does anyone except UNIX coders?)

if you are curious the relevant portion is here => https://www.dropbox.com/s/hszxozv974u36y5/~CRASH_2014%3A06%3A13-%C2%B116-07.rtf

(testing out my new DropBox account)

CCC

Reply

Answer 4

BDAqua

Level 10

239,225 points

Sep 24, 2015 10:50 AM in response to ChitlinsCC

We need to see this...

/Library/Logs/CrashReporter/loginwindow.crash.log

Yiu can paste the text from Console directly here.

Click on the top line we want, Shift plus click on the bottom line we want, CMD+c to copy, then paste the text in a reply with CMD+v

A few dozen lines should be about right, hundreds or thousands won't likely be readable. 🙂

Reply

Answer 5

ChitlinsCC Author

Level 7

20,924 points

Jul 14, 2014 10:46 AM in response to BDAqua

BD....

OK, you asked for it... Through THREAD 0...

Host Name:	RoadRunner
Date/Time:	2014-07-13 16:07:40.423 -0500
OS Version:	10.4.11 (Build 8S165)

Report Version: 4

Command: loginwindow

Path:

/System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow

Parent: launchd [1]

Version:

4.7.5 (4.7.5)

Build Version: 1

Project Name: loginwindow

Source Version: 11700600

PID:

66

Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)

Codes:

KERN_PROTECTION_FAILURE (0x0002) at 0x0000005c

Thread 0 Crashed:

0 com.apple.AppKit	0x937d6624 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 1720
1 com.apple.AppKit	0x937f6c94 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 192
2 com.apple.AppKit	0x937cfca4 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 384
3 com.apple.AppKit	0x937c4f98 -[NSView displayIfNeeded] + 248
4 com.apple.AppKit	0x937c4e08 -[NSWindow displayIfNeeded] + 180
5 com.apple.AppKit	0x937c4cb4 _handleWindowNeedsDisplay + 200

6 com.apple.CoreFoundation 0x907de570 __CFRunLoopDoObservers + 352

7 com.apple.CoreFoundation 0x907de810 __CFRunLoopRun + 420

8 com.apple.CoreFoundation 0x907de2b0 CFRunLoopRunSpecific + 268

9 com.apple.HIToolbox	0x932adb20 RunCurrentEventLoopInMode + 264
10 com.apple.HIToolbox	0x932ad12c ReceiveNextEventCommon + 244
11 com.apple.HIToolbox	0x932ad020 BlockUntilNextEventMatchingListInMode + 96
12 com.apple.AppKit	0x93791734 _DPSNextEvent + 384
13 com.apple.AppKit	0x937913f8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
14 com.apple.AppKit	0x9378d93c -[NSApplication run] + 472
15 com.apple.loginwindow	0x00005aec 0x1000 + 19180
16 com.apple.loginwindow	0x00005404 0x1000 + 17412
17 com.apple.loginwindow	0x0001965c 0x1000 + 99932

CCC

Reply

Answer 6

BDAqua

Level 10

239,225 points

Jul 14, 2014 4:22 PM in response to ChitlinsCC

Was it running Safari or maybe Flash at the time this happened?

Reply

Answer 7

ChitlinsCC Author

Level 7

20,924 points

Jul 14, 2014 5:12 PM in response to BDAqua

BD.....

Neither - even since startup Pismo.

OpenApps:

App = #windows

FF = 3tabs(all ASC)

Entourage = mail & signatures

Grab = 0 windows

XBattery = 4 windows

ActivityMonitor = Active Processes & CPU floating Guage

DropBox = not really 'windowed' much (like iCloud) shows as folder in SideBar like Desktop, Applications, etc

±180MB RAM = free ±90MB = inactive (best guess, of course - if average)

FF recovered all tabs

All Apps open up at login except Grab

Reply

Answer 8

BDAqua

Level 10

239,225 points

Jul 14, 2014 6:43 PM in response to ChitlinsCC

I have had strange things happen, though not exactly that, with less than 200MB of RAM... less so with 10.4 than higher OS versions.

Reply

Answer 9

ChitlinsCC Author

Level 7

20,924 points

Jul 14, 2014 6:58 PM in response to BDAqua

SOP on my Pismo and never happened before or since.

I didn't wanna influence anybody's thoughts on the matter, but I guess we are about to agree that weirdness happens occasionally.

Odd that actions in System Profiler (very deep level OS & hardware monitoring & data collection) seems to be the obvious culprit in the system crash. At first, it really looked like a Windows crash, except that it recovered by itself.

Ah well... one of life's great mysteries.

CCC

EDIT

To be clear, OP states 512MB installed RAM - prior post approximates 200MB free/available.

Reply

Answer 10

BDAqua

Level 10

239,225 points

Jul 14, 2014 11:35 PM in response to ChitlinsCC

I guess we are about to agree that weirdness happens occasionally.

Yep. 🙂

Reply

Answer 11

rccharles

Level 6

12,957 points

Jul 16, 2014 2:31 PM in response to ChitlinsCC

Try running in safe mode if problems persist.

hold down shift key when booting ... i think.

I'm no expert on reading these things, but...

Crashed when drawing a rectangle on the screen??? video problem? lot of display threads.

Why all this stuff about login? The machine was running for awhile after login wasn't it? Maybe it is a unix thread login.

Reply

Answer 12

ChitlinsCC Author

Level 7

20,924 points

Jul 16, 2014 3:55 PM in response to rccharles

rcc........

Read the OP. I have no clue what any of the logs mean, only that it clearly corresponded to the time of the ONE-TIME event. Cannot replicate so no need to try safe mode.

CCC

😕

Reply