51037 Views Previous 1 … 6 7 8 9 10 Next 147 Replies Latest reply: Aug 3, 2010 1:22 PM by alialib Go to original post
I've had a forced log out three time just today. I occasionally use Photoshop or Illustrator CS. I know I always had Firefox running. I can tell you I was told to erase down to zeroes, reinstall, and move files over. The good news is I went from 20 GB free space to 200 GB. I'm only moving stuff over as I need it. The bad news is I'm still having problems under SL.
Console lists a *Segmentation Fault* at the time of crash. What exactly is that? Sounds like some sort of directory error.
In the crash log reports, the logs always starts out with:
Process: WindowServer [####]
Path: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/WindowServer
The beginning of the log has:
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x00000001747ed03a
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ...ple.CoreServices.CarbonCore 0x00007fff85dd82a6 UCKeyTranslate + 464
1 com.apple.CoreGraphics 0x00007fff87c1ad79 CGSUniCodeForKeyAndFlags + 161
2 com.apple.CoreGraphics 0x00007fff87c9088b CGXCheckForHotKey + 3184
The problem is not with our apps. We all know what the problem is. *Snow Leopard*. It's the most unstable OS I've seen, and I've been a Mac user since at least OS 6. Get the bugs out Apple.
I had the same problem with both FM8 and the FM7 while entering data. It happened about 4 times and then I came here. I made the preference changes you suggested and we'll see what happens. I just bought a new MacBook Pro with the Snow Leopard upgrade and if this does not fix the problem, it's back to the iBook.
I also made sure to install all available updates to the my Filemaker, and I have had a logout since, but it seems to be much less frequent. I think this supports my idea that the autosave is in conflict with other system operations, i.e. b/c it's writing much less frequently, there's less of a chance of conflict. I've also seen weird behavior if the file is in my Dropbox. In case you don't know what that it is, Dropbox automatically syncs a local folder to a remote web directory (a great and free service). When the file is in the local Dropbox folder, I see via Growl notifications that it is saving out repeatedly and creating conflicting versions.
I am also using Filemaker Pro Advanced 8.0, but I doubt there's enough difference b/w 7.0 and 8.0 to make a difference. You might try setting to 30 minutes or longer and see if that helps.
As for what precipitates the logout, tabbing between fields will cause the cache to update so it may still be this caching problem. Of course, it's really a Snow Leopard problem that Apple needs to fix. I know they want to shed legacy software support so they don't have a great incentive to make Rosetta work well, but we paid for this freakin' update and they need to take care of us.
Anyone know if they are indexing the drive differently under Snow Leopard? It also seems that the heretofore useless Spotlight works much better, so maybe the indexing scheme is different and is involved in causing the problem.
I'm in a similar situation where Excel 2004 causes WindowServer to crash and logs me out. Tried everthing here including clearing ram, disabling dup fonts, cleaning login items, repairing disk permissions, reinstalling 10.6.1, and clearing preferences. Have sent crash files to Apple product specialist and he's going to "send it to engineering". However, I keep getting told by the specialist that if the application is crashing the system they won't be able to help me and I have the choice to either upgrade to Office 2008 (i.e. spend more $) or stop using that application. He said that Apple would never claim that they support Office 2004. I wonder why they sold it through their stores then. I'm very disappointed at such a response considering this application is the most used productivity software! Wondering if I was duped by the mac-vs-pc ad where they make fun of PC tech support problems due to 3rd party hw/sw providers, or the one where the Yoga instructor is mad that her applications cripple her PC. If OS X has the same problem, does this constitute false advertising? Seriously considering going back to PC if this can't be fixed.
I just got a new mac mini to replace an old IMac that I had. I installed some older programs that I had, Photoshop 3, and Office 2004. While running excel, and word I have gotten the blue screen and then back to the desktop, just like everyone describes. The last post suggest it's a RAM issue, maybe not software as much. I only have 1MB OF RAM, and It's random when I get logged out.
I've had while in excel, 3 times in a row. Word twice in an hour. And today while trying to reinstall Photoshop 3, no office program open, was kicked out. It seems that Snow Leopard doesn't like older programs, but I don't think Apple has ever liked old programs(anything 3 years and older.) All the new programs work great.
I have a shiny new MacBook Pro with 4 GB of RAM, so that can't be the answer to my particular problem. I have yet to do any database work in Excel on this new machine, but will report what happens when I do. I would hate to think that I will be forced to buy Filemaker 10 just to get Filemaker to work with Snow Leopard.
I am still having ongoing problems with Office 2004 since upgrading to SL. The only answer I have received from Apple is that it must be a Microsoft problem and they seem to have little interest.
I am very disappointed as I have been an Apple owner since Apple IIc days (about 20 years?) Has anyone had ANY feedback to indicate that they are even looking into this problem? Does anyone know if Microsoft is due to release a new Office for Mac in the near future as I don't want to buy 2008 if it is about to be superseded.
I was also about to buy two more Macs but am seriously thinking twice now.
The problem is not with Office 2006, or Filemaker, or Eudora, or older version of Photoshop, or any other app that this is happening with. It is with Rosetta which runs older PowerPC apps on Intel machines.
Apple is aware of the problem - but whether they intend to get it fixed is not clear.
Rosetta was not actually created by Apple app, so they probably have to get the company that created it to fix it.
Apple has no long term interest in Rosetta. OS 10.7 likely won't even run PowerPC apps. They'd prefer it if everyone just went out and bought new Intel versions of the various software apps.
On the other hand, this bug is not at all good for Apple's reputation. After years of working with a very stable system that hardly ever crashed, there are now thousands of users (judging from complaints on many different forums on the web) finding their system crashing several times a day - and a number wondering whether they should go back to Windows.
But the more poeple that fill in bug reports or can bend the ear of Apple executives the better for everyone - Apple included.
I waited for the release of 10.6.2 to try and solve this problem...but it doesn't for me. I'm not running Excel or anything of the sort, and as far as I can tell it happens when the screen saver is about to kick in. Or should I say it seems to happen if I leave it open and walk away - I come back to the login screen. I'm trying to find anything on the console that gives me any more info...but nothing obvious. Are others still having this problem with after updating?