50729 Views Previous 1 2 3 4 … Next 147 Replies Latest reply: Aug 3, 2010 1:22 PM by alialib Go to original post
I am having the same exact problem. I am constantly using Excel and I run an external monitor but my Mac started doing this a couple of weeks before Snow Leopard. I had hoped that Snow Leopard would cure it but it hasn't.
I have a theory. _Microsoft released an Office 2004 update Thursday, August 13, 2009_. That is curiously near when I started having problems. Perhaps others who are having problems only since Snow Leopard didn't upgrade and use Excel between that update and Snow Leopard.
If I'm correct, what do we do? Are we all using Excel 2004 or is anyone having this with 2008? I hate to upgrade Microsoft office to make it stable, but I need my machine to work.
Glad (?) I'm not the only one. This has happened to me mostly in Eudora, but often in Photoshop CS2. I've been trying to troubleshoot and it seems like it's not related to:
1. having a firewire hd connected
2. having an external monitor connected
3. having a usb keyboard/mouse connect
It may be keypress related...I'm almost scared to use cmd-w to close windows and I click the close window button whenever possible. But just typing any key in Eudora and Photoshop CS2 can cause the spontaneous logout. And there's no rhyme or reason...sometimes it'll happen several times in a row...sometimes I'll go almost an entire day with no logouts.
MacPro 2x2.8 Quad 10.6 (build 10A432)
Network, wired ethernet
Connected to external monitor via mini display port.
All software patches up to date.
I also am experiencing the random logouts.
Blue Screen, Login Screen, - Login is as if nothing happened.
Noticed that when I went to reconnect to my servers that they were highlighted as I had previously randomly chosen my mount points. (like it remembered what volumes were there before "event"?)
*"It may be keypress related...I"*
I did not even install Rosetta and am using the most current versions of CS4 and Microshaft Enoturage,word,excel (though 04' is installed) So am not convinced it is a specific piece of software
I too think that when this has happened I have been depressing or manipulating a quick key to perform something.. I use so many keyboard shortcuts that some times I accidentally overlap sequences and do things like launch FrontRow on accident.. maybe something to this.. going to dig into the keyboard and universal access prefs again..
I've got some crashes this morning:
I'm with 10.6.1 on MacPro and was using Backup 3.1.2 (374) when crash started, files found at /Library/Logs/DiagnosticReports:
(I've modified the crash files names to be sorted in the right order (put date and time at first in the file name):
Within 44 sec SL logout and ask for logging 4 times ...it was very fast and since then nothing happened, crossing fingers ...will see by tomorrow again with backup ... but after the last crash I restarted backup and it worked flawlessly, I don't think that Backup is responsible for this, WindowServer is crashing so nothing work anymore.
"blued" is the Mac OS X bluetooth daemon, and I don't have any bluetooth on MacPro...
This morning Backup worked very well, no more logouts, here under beginning of 2009-09-12-090856WindowServerlocalhost.crash file:
Process: WindowServer 
Path: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/WindowServer
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd 
Date/Time: 2009-09-12 09:08:54.286 +0200
OS Version: Mac OS X 10.6.1 (10B504)
Report Version: 6
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff86cc5ff6 __kill + 10
1 libSystem.B.dylib 0x00007fff86d67072 abort + 83
2 libstdc++.6.dylib 0x00007fff883a75d2 _tcf0 + 0
3 libstdc++.6.dylib 0x00007fff883a5ae1 _cxxabiv1::_terminate(void (*)()) + 11
4 libstdc++.6.dylib 0x00007fff883a5b16 _cxxabiv1::_unexpected(void (*)()) + 0
5 libstdc++.6.dylib 0x00007fff883a5fd6 std::bad_cast::what() const + 0
6 libGLProgrammability.dylib 0x00007fff8865a064 TPPStreamCompiler::newNodeFromOperand(ParseOperand*) + 84
7 GLEngine 0x0000000113e070a2 gleFreeShaderObject + 69
8 GLEngine 0x0000000113d242c2 gleDeleteHashNameAndObject + 121
9 GLEngine 0x0000000113e06fa9 gleFreeProgramObject + 371
10 GLEngine 0x0000000113deac13 gleUnbindDeleteHashNameAndObject + 146
11 GLEngine 0x0000000113d77031 glDeleteObjectARB_Exec + 318
12 com.apple.QuartzCore 0x00007fff87422892 CA::OGL::gldeleteshader(CA::OGL::GLShader*, CA::OGL::GLShader*, void*) + 31
13 com.apple.QuartzCore 0x00007fff872176a8 xhash_tableforeach + 75
14 com.apple.QuartzCore 0x00007fff8725c901 CA::OGL::GLContext::purge_shaders() + 123
15 com.apple.QuartzCore 0x00007fff8725c877 CA::OGL::GLContext::purge() + 17
16 com.apple.QuartzCore 0x00007fff8725c850 CARenderOGLDestroy + 18
17 com.apple.CoreGraphics 0x00007fff87a888d6 CGXGLAccelComposite + 1606
18 com.apple.CoreGraphics 0x00007fff87a87552 CGLayerComposite + 242
19 com.apple.CoreGraphics 0x00007fff87a635b9 CGXUpdateDisplay + 7042
20 com.apple.CoreGraphics 0x00007fff87aba7f3 CGXFlushWindowList + 709
21 com.apple.CoreGraphics 0x00007fff87aba52b CGXFlushWindow + 33
22 com.apple.CoreGraphics 0x00007fff87aba49c _CGXFlushRegionInline + 204
23 com.apple.CoreGraphics 0x00007fff87aba3c6 _XFlushRegionInline + 176
24 com.apple.CoreGraphics 0x00007fff87a9457d CGXServices_server + 108
25 com.apple.CoreGraphics 0x00007fff87a9423a connectionHandler + 220
26 com.apple.CoreGraphics 0x00007fff87a766c1 CGXPostPortData + 175
27 com.apple.CoreGraphics 0x00007fff87a764cb CGXRunOneServerPass + 451
28 com.apple.CoreGraphics 0x00007fff87a737e6 CGXRunOneServicesPass + 357
29 com.apple.CoreGraphics 0x00007fff87a7c3ea CGXServerLoop + 139
30 com.apple.CoreGraphics 0x00007fff87a47bd6 CGXGetRootAdminCredentials + 0
31 WindowServer 0x0000000100000f29 main + 9
32 WindowServer 0x0000000100000f18 start + 52
If interested I can post more.
IMHO OSX doesn't crash but only Window Server, so no proposal to send files to Apple, how to send crash report files to Apple ?