I had a persistant problem where the CS6 trial of Photoshop crashed on 'Save As' under a new install of Mountain Lion.
After 3 days, and many re-installs, I tracked the problem down to 4 installed fonts, two of them Adobe font suitcases.
They are...
#PCmyoungjo.dfont
#Pilgiche.dfont
Adobe Sans MM
Adobe Serif MM
Removal of the above, which checked out fine using Font Book, also stopped my Office 11 suite from crashing on startup.
I had also removed every faulty font from my list of 2100+ fonts, and only when a clean install with the minimum of fonts worked, did I try dragging extra fonts in a few at a time, then, Bingo! Crashes.
CS6 worked fine under Lion with the full font list, so obviously something dramatic has changed in Mountain Lion regarding handling fonts.
Thanks for reporting back. Apple has been inept at handling fonts from day one, and Photoshop has always been very susceptible to crashing because of bad fonts.
Those first two fonts are Korean fonts from way back in the Panther days (OS X 10.3).
The Adobe Multiple Master fonts are also legacy fonts that haven't been needed for a long time..
FontAgent Pro (FAP) is pretty good at ferreting out problem fonts, including some that both Font Book and Mac FontDoctor miss. There's a fully functional 3--day trial version at their site,
Nothing like an erase and install when going to a new OS. I'll never understand why Apple provides all this "migrating" possibilities. They bring nothing but grief!
That worked for me. I had copied the contents of my (many years old) "favorite fonts" folder into my new ML install, and then, BANG, no Adobe product would run for me. (Shame on me for not being more careful.)
I removed these fonts you listed:
#PCmyoungjo.dfont
#Pilgiche.dfont
Adobe Sans MM
Adobe Serif MM
And now my CS6 Production Premium apps all seem to be running fine.
I wish Adobe Apps would check for problems like this during startup, rather than just crashing without giving a clue as to the problem.
Thanks for the tip.
I'm no expert, so do this at your own risk --
I just looked in the /Library/Fonts folder on the main drive and manually found the font files with the names above (as mentioned before, arrange the folder by name and the will fall in alphabetical order). I then just dragged them (and only them) to the trash. I then re-started the computer and all was well.
If these instructions make you uncomfortable, you probably shouldn't be mucking around in your system by yourself. If that's the case, you should find local help in person with someone who has experience with Macs before you go any further.
Good Luck.
It's possible that the Fonts are in the User Library. This Library, by default, is hidden in Lion and Mountain Lion.
To open it, click on the desktop to select the Finder, then in the 'Go' menu, select 'Go to Folder', then in the dialog box type in ~/Library
Once open, search for the Fonts folder.
Regards
Santa
I've written a quick Applescript that will remove the offending Fonts, and opens the two Library Folders for visual checking.
Take note that if the offending fonts have been renamed, they will not be removed by this script.
To run this, open Script Editor in your Applications Folder, paste the text below into the window, and click 'Run'.
Regards
Santa
set ptl to path to library folder
set ptul to path to library folder from user domain
set ptlf to ptl & "Fonts" as text
set ptulf to ptul & "Fonts" as text
set FontsList to {"#PCmyoungjo.dfont", "#Pilgiche.dfont", "Adobe Sans MM", "Adobe Serif MM"}
repeat with ThisFont in FontsList
set FontToFind to ptlf & ":" & ThisFont
tell application "Finder"
if exists FontToFind then move FontToFind to trash
end tell
set FontToFind to ptulf & ":" & ThisFont
tell application "Finder"
if exists FontToFind then move FontToFind to trash
end tell
end repeat
tell application "Finder"
open ptl
open ptul
end tell
Thanks for taking the time to provide this script Santa. I have run it and unfortunately the issue still occurs. I find Dreamweaver works on occasion but in the majority of cases crashes. In the meantime, I have installed a virtual machine with Lion and am running CS5.5 there until Adobe or Apple come up with a fix. Hopefully it won't be too long.
MARCELLO PAIVA wrote:
...How do I know if there are more offending fonts installed?...
As per post #1:
FontAgent Pro (FAP) is pretty good at ferreting out problem fonts, including some that both Font Book and Mac FontDoctor miss. There's a fully functional 3--day trial version at their site.
Hi Karl,
Hearing your issue, I agree that you should be able to have any fonts you want on your system. But at the same time it is likely that some of the fonts you have are outdated or corrupted.
Rather that fighting to keep every font you have installed, have you considered starting "fresh" with only the default fonts of a fresh OS install, and then adding back your favorites a few at a time untill you find the bad ones? That more systematic approach would probably help you ferret out the problem font files and allow you to know exactly which ones you'll have to do without.
Try that, or FontAgent, or both, and post back here what you found.
Hi EPickart, it was Marcello who mentioned about wanting additional fonts. I did a fresh install with only the default fonts and put CS6 on top and still had the same crashing problem, so unfortuantely it doesn't seem like a font issue in my case. Still very keen to hear others' experiences in case I might have missed something.
Karl
Karl,
I see I did mix-up your two posts. I'm using the production premium package - but I'm a video editor using PS, AI, AE, EN, & PR. I've never even installed Dreamweaver, let alone run it, so it does sound likely to be a different problem. Do you use a second video monitor for your work? One of the things I ran into while chasing this down for myself was a couple of forums with people saying they had video driver conflicts....
Good luck.
Hi all, by way of update. I installed all updates, Mac OSX 10.8.1 and all Adobe CS6 updates and now the crashing problem is not occurring for me. Dreamweaver and Fireworks seem to be opening without any problems and even after several days of use, the problem has not come back. I hope this helps everyone else too.
North America
Europe, Middle East and Africa
Asia Pacific