One thing I have seen that I haven't seen mentioned on this thread is that for some reason, SL wants PS's Scratch Disk to be set to the Boot Disk. So if, like me you had the Primary Scratch disk set to another dive, set it back to your Mac's boot disk and see if that helps.
ATI 3870 here, with lots of crashes.
If CS4 did not crash in Leopard you could always test by copying the ATI drivers from Leopard to Snow Leopard and see if that makes any difference. Be sure to save the Snow Leopard drivers so you can copy them back.
I have been all over the forums trying to stop getting emails from
every post on this thread. The site indicates that it's turned off,
I've NEVER asked for these emails before and have never gotten them
before. How do I stop getting an email every time someone posts to
this discussion? Thanks!
For the past 5 days I've been cruising the internet forums, blogs, and communities, including this one, in search of an answer to my CS4 crashing issues...
A common factor that I'm finding across the board, is that people complaining about CS4 crashing own ATI graphics cards. So in hopes that we may be closing in on the cause of this problem... who out there is having crash issues that have an ATI card with CS4 + Snow Leopard.
On open / saves on PS, ILL, and InDesign, especially exporting PDFs from InDesign the program simply crashes/closes. Also, placing new links/photographs crashes. No pinwheel of death, no freezing. The program simply shuts down. Often times a crash report doesn't even come up for Adobe or Apple.
I have this issue on 2 different computers - a MacPro and my MacBookPro - both sport ATI cards.
You seem motivated so I'll reply to you :-)
The way to approach this is to use something like Crash Reporter: http://en.wikipedia.org/wiki/Crash_Reporter_%28Mac_OS_X%29
I have never dug into these tools on OS X as I spend most of my time using Linux as a desktop and my (daughter's) iMac with SL and CS4/PS (with ATI card) has no problems.
It looks like one can increase the verbosity of Crash Reporter without having to install CrashReportPrefs from the Developer Tools by running (from a terminal command window):
defaults write com.apple.CrashReporter DialogType developer
You probably have to prefix that command with sudo, i.e.:
sudo defaults write com.apple.CrashReporter DialogType developer
and you will be prompted for your user password.
Hopefully once you have increased the verbosity using the above when a CS4 app crashes it will display some debug information. If enough people post debug info perhaps some commonalities would surface
Shark looks even more full featured but requires a greater effort.
Hope this helps.
I did a simple upgrade from Leopard 10.5.8 to Snow Leopard today. I run Creative Suite 4, primarily Photoshop 11.0.0 and Illustrator. I didn't not have any problems using Illustrator but Photoshop crashed every time I tried to save a file, specifically with the "Save for web" dialog. I upgraded to 11.0.1, and removed all third-party plugins, but the problem persisted. I uninstalled Photoshop with Adobe's uninstaller and then reinstalled Photoshop and upgraded again to 11.0.1, but the problem persisted.
I was able to duplicate the crash 100% of the time. Once I saved a file for the web, Photoshop simply crashed without an error message. I was only met with the Crash Report utility.
I was able to avoid a crash by disabling the OpenGL option in my Preferences > Performance. Immediately upon deselecting this option I was able to successfully save the for the web without a crash. I have not yet reinstalled third-party plugins to test further.
I hope my experience helps someone out there as this is a very frustrating issue.
Below is the profile for this particular system. Not the video card as this may be related to the problem.
Model Name: iMac
Model Identifier: iMac9,1
Processor Name: Intel Core 2 Duo
Processor Speed: 3.06 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: IM91.008D.B08
SMC Version (system): 1.45f0
Chipset Model: ATI Radeon HD 4850
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: ATI (0x1002)
Device ID: 0x944a
Revision ID: 0x0000
ROM Revision: 113-B9090C-181
EFI Driver Version: 01.00.327
Resolution: 1920 x 1200
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Chris Cox wrote:
Smellkid - please read the existing replies before posting.
Crashes on save and open (and lots of other times) are a common problem in MacOS 10.6, in many applications.
Apple is working on it.
This is not a common problem. Yes some people are having this problem but not all of us. I have not had one crash on save and open yet.
And there is a reason some of us are not having this problem.
I am using:
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
... and crashing all the time. Re-installed SL and re-installed PS CS4 - no improvement.
Thanks for your post on this subject. It's good to hear from someone that the problems being reported are seen as valid.
There are, of course, two crash reporters. Apple's and Adobe's. Does Apple share data with Adobe, or does anyone know whether Apple has acknowledged this problem?
Also, I most certainly hope that Adobe is getting the right data. The latest crash that I experienced (opened a JPEG, modified it, then tried to save the modified version with a different name) generated Apple and Adobe crash reports, but when I looked at the crash data to be sent to Adobe, I found that it was pointing to an XQuartz crash, not the PS crash.
Uh, just to make myself feel better, I'm appending it to this posting.
Can I presume everyone else out here is seeing the same thing?
Finally, my own personal opinion: I haven't upgrade any critical systems to Snow Leopard as yet. I think issues like this are to be expected. Chris, I just would ask whether there is one place you can point CS4 (PS and the suite in general, since I like others are seeing this in all of the CS4 apps) for updates? It'd be good to know asap about any workarounds or solutions that are developed.
Message was edited by: KMPetersonBoston - filetype "crash" apparently not allowed, changed to .txt
No problem here. Mac Pro 2008 with 6 GB of RAM, Radeon 4870. I installed on top of 10.5.8. So far so good. It this problem is exclusive to certain systems, I would think that the problem systems all have something in common. Is something modified on a clean 10.6 install that remans unchanged on an upgraded system?
Apple has acknowledged this problem?
Yes, Apple has acknowledged the problem. They are working on a solution now.
We're still gathering the crash reports for MacOS 10.6. It takes time, because the TFSInfo crash happens all over the place.
There are other Apple crashes that also happen in multiple places, but less often. We're trying to narrow down the circumstances of those crashes and document them for Apple.
We don't have any updates yet, but you should keep an eye out for updates from Apple.
Unfortunately we don't know details of the bugs in Apple's code, so we don't know of any workarounds at this time.
Photoshop CS4 runned like a clock on Leopard. On 10.6 (updated) i get in all kinds of strange problems.
1. Getting "Could not save "File.psd" becuase the file is already in use or was left open."
The only app that has the file open is Photoshop. I got no other apps even running. I turned of Spotlight for all the directories (app directory, cache directory, File directory and so on). The only way to get rid of it (for a couple of hours) is to reboot.
2. Yesterday there was a new "error" message. Totally new. "The disk copy of "file.psd" was changed since you last opened it. Do you want to save anyway?"
I reproduced the problems with restarting. Turn off spotlight, Launch only Photoshop. The strange thing is that the feeling is that the errors come random. Can work for a couple of hours without glitches. Then it pops up.
It's not a serious problem. But it's annoying.
Those sound like some part of the OS, or some other app you have installed, is playing with the files while you work in Photoshop.
Both messages mean that something OUTSIDE of Photoshop has locked or changed the file.
Sigh.. Just installed the Snow Leopard 10.6.1 update but photoshop still crashes at the same point (about 10% in opening a 1.2Gb file).. I guess this makes the chances of a swift solution from Apple smaller as i dont see them releasing updates weekly..
I also installed the 10.6.1 Update, and just worked on and saved four largish TIFF's in a row! Woohoo. I haven't, however attempted to save any JPG's yet. But, it is definitely an improved situation.
Model Name: iMac
Model Identifier: iMac4,1
Processor Name: Intel Core Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
I think this problem is not as widely pervasive as some might think. My Mac Pro is running just fine, no crashing, no issues. So that leads me to believe that is has to be something commonly found in certain setups but not on all setups. I am using only moder Open Type fonts on my system, and I am not sure if this might have a baring on things, but in the past, I have had issues with certain applications misbehaving due to a corrupted font, or an old font format that is no longer fully supported on OSX. I have not had any problems whatsoever, so why are some having such a hard time an others are not?
I think it has something to do with fonts too. I have not had a crash since I upgraded to 10.6. I use FontAgent Pro and have it manage my system fonts. I have also disabled all the fonts that FontBook will allow me to disable.
Exactly, I have a Mac Pro too and it's running smoothly. No crashes at all.
It's my MBP that's giving me such a hard time...
I can't think of specific differences between the two systems other than drivers and hardware-related stuff. But I see that other MBP owners aren't experiencing such problems, so I'm left wondering where the problem could come from...
Hi. I have a white MacBook 2.2GHz 4 GB RAM and installed Snow Leopard last Sat and Photoshop CS4 seems to be working much faster opening files, just a faster workflow, much better performance than 10.5.8. But anytime Apple releases a new system it's a crap shoot for some until all the bugs are worked out. Hope everyone gets up and running soon.
I haven't installed Snow Leopard yet, and won't do so till I get assured that all those bugs have been resolved, but, just for arguments' sake, how to proceed to check if a certain fon type is causing all that havok?
how to proceed to check if a certain fon type is causing all that havok?
One thing I should note before anything else is mentioned. Search all you Fonts folder and make sure you have no duplicate fonts.
First of all I would clean all caches and then reboot. If you are still having crashes then start on fonts. A font manager would come in real handy here.
Disable all fonts except the necessary system fonts. Clean the font caches again and reboot. If your crash free now add a few fonts back in at a time. If crashing starts you can probably narrow it down to the last fonts you installed.
I agree what DYP said, and you need to realize that a large percentage of us in this forum have 2000-5000 fonts to manage.
I use font doctor to fix things like duplicates, damaged fonts, etc in my font library. I advocate using font agent pro as well for management. I run coctail, reset the PRAM, disk warrior, and sign on as a single user using fsck -fy sometimes. I'm not sure if this helps you, but I use ifreememory to keep my system running as fast as I can push it.
With all of this going on, I have never had a problem with the PSC 4 suite.
I've been using "Snow" for several days now and the above makes things work "perfecto".
Things seem to be pointing to Snow Leopard no longer likes Postscript type 1 fonts, while Leopard did. It seems from reading posts these may be carry overs from some installers, could even be Adobe's, in the users home folder/Library/Fonts folder. Use Apple's Font Book to resolve duplicates and validate your fonts and then use the updated FontNuke 1.1.6 to clear cached copies. See if that helps.