CS crashes then won't re-launch- stuck at initializing

312 views8 repliesLast post: 8/12/2004
We just got Dual 1.8GHz G5 and have Photoshop CS running with 1.5 GB Ram on the system. Everyday it seems that Photoshop will crash. When trying to relaunch the program, it will stick at initializing and go no further. We have to reboot the system to get Photoshop to work again. This should not be so. Has anyone else seen this. I haven't tried re-installing yet, as it is a pain, but I may have to.
#1
I have the same problem occasionally with my G4 1 GHz (gig of ram) Powerbook running 10.3.4. It is especially prone to happen when I am launching a number of programs at once - so may be a problem involving the window server in some way. At any rate, this never happened with Photoshop 7. In those cases I too have to reboot the computer to get PS CS to launch properly. I can force quit the stalled launch, but then it still won't relaunch all the way - and gets stuck again.
#2
Never had this issue on our ibook G3, just since we've moved to the G5 tower does it exhibit this problem. Wish someone would know why.
#3
G4 Sawtooth 450 MHz, MacOS 10.3.4.

For me 7.0.1 recently started hanging during launch or crashing near the completion of launching. _Never_ any problem like this before. I can't think of anything about the system that's changed in the meantime except MacOS itself. Unfortunately, I don't use Photoshop often enough to correlate this with 10.2 -> 10.3 or a subsequent minor update.

I tried troubleshooting by deleting preferences as recommended by "gballard" referenced in a previous post. No help. (Well, launching seemed much faster, but the result was still the same.)

Since Photoshop launches and works perfectly for what I've tried after restarting MacOS X --repeatable, at least twice-- I've concluded that the Photoshop application installation itself is probably not corrupt.

More ideas?
#5
The prime suspect is a corrupt font.
#6
Ramón:

Thanks for your response on this thread.

I've cut way back on fonts -- I have removed almost everything except the bare minimum, which decreases the likelihood that a font is at fault.

But if a font is corrupt, why would it be OK for "a while" after a fresh startup?

Thanks,

Henry
#7
Henry,

I was actually addressing Mark Bolicks original post, but I see no reason why my response could not apply to your problem.

Corrupted fonts can indeed cause intermittent problems.

On the other hand, there's no guarantee it's a font. I just observed it would be a prime suspect, not the undisputed culprit. :)
#8