Photoshop CS5 freezes

[Yefolio-KBIqSr]

Hi,

Have been using PS CS5 since the trial became available. But seems CS5 responds a lot slower than CS4. Sometimes, it just freezes or slow the whole computer down when I tried to open a many-layer file. I had to force quit the application, It's really frustrated because the system responds very slow even I tried to quit PS. Once it's quite, everyting's back to normal. Does anyone have this problem?

Thanks,

[CDPritchard]

It might also help to know that the freeze is sometimes accompanied by a huge CPU jump by ATSServer in Leopard (jumped to 80% on freeze, then back to zero on foce quit PS). Other times it isn't, but in those cases windowserver seems to be the one with the jump.

[Chris Cox]

Yeah, this is looking more and more like a problem with event handling and Window Server.

We're trying to reproduce it here, but haven't been able to so far.

And we're trying to visit customers reporting the problem - but don't have many close to our offices yet.

[toxic waltz]

Get me a machine and software and I'm sure I can run it into the ground.

[Guest]

Chris Cox wrote:

Does this only happen when working on document with many layers (and maybe layer groups)?

Do you get the slowdowns and freezes if the layers palette is hidden?

Behaves this way on  flattened images, as well as those with layers...same behaviour with layers pallet hidden -- system slowdown. And, as always, the OS issues a crash report on program shutdown (which can go on for up to 30 minutes).

Here is a link to our Mac crash report file (rtf): http://files.me.com/contre_jour/pwa55q

Regards,

Garry, co-owner, Contre Jour Studios.

[Chris Cox]

Garry - that's a crash while quitting Photoshop (that the service manager team is working on).  That probably isn't related to the system slowdown.

[Nov1]

It happend to me again. Shortly after opening a large PSD with lots of layers, I opened the Character panel, resulting in a system stall (is the best description I guess). I waited it out and forced quit. Than I tried to reproduce the stall by repeating all of the steps. Only this time everything worked fine. I know this is really aggravating for a bug fixer... but I'm also trying to understand what is causing the problems.

@Chris; if you want to, I can send you the 'problem details' wich was generated after I managed to forced quit.

[_scott__]

Just to mix it up a bit more... and cause further unintentional frustration.... I have yet to even touch the Type tool in CS5. The freezes are so apparent here that I haven't even considered using the text tool. So, the system sluggishness I see has no correlation to selecting or using the Type Tool.

[Chris Cox]

Scott - if font previews are turned on, then type can be rasterized for the previews even without touching the type tool.

And it happens in the background, so any problems would occur a while after launch.

[toxic waltz]

So much for quality beta testers.  Must be a thing of the past.

[_scott__]

Chris Cox wrote:

Scott - if font previews are turned on, then type can be rasterized for the previews even without touching the type tool.

And it happens in the background, so any problems would occur a while after launch.

No font previews here, Chris.

[Chris Cox]

Grr.  I have a feeling I'm going to have to FedEx a whole system before this is solved....

[_scott__]

I'm wondering if the majority of us having the issue are using a Mac Pro 1,1 ?

I've seen several post that they are, and I am.

[Chris Cox]

So far we have MacPros and MacBooks.

But we're still investigating (and there's always the chance that there is more than one cause, or someone misunderstood the description).

[ashlie_h]

I'm on a MacMini and I went though all the fonts, couldn't find any with problems. I've changed permission settings. I just had it happen again. I was able to eventually open a terminal and run top. The windowserver was going crazy and as soon as it stopped the compter was usable again. Everything on the computer starts running incredibly slow when it happens.

[Chris Cox]

Yeah, if WindowServer gets confused EVERYTHING will grind to a halt (slow to unuseable).

We've seen that happen before (like when someone opened 600 document windows at once).

[C-Wave]

Chris-

Don't forget to include MacBook Pros on you list.  Thanks for trying to get to the bottom of this.

[Chris Cox]

Nov1 - it might help, email it to ccox at adobe dot com.

[Mike_Ornellas]

I need a machine, the software and this stupid sensorship removed from my account.

I dont plan on purchasing anything at this point for the sake of Adobe.

[ashlie_h]

I don't have dual monitors and still get the problem. I'm going to try cleaning out my fonts completely and see what happens.

[lkemper]

My MacBook Pro is not crashing (desktop is) but when I paint with a large brush on a moderate file (120MB) ,on the laptop, and use a 500 + pixel brush I can have a 5000 x 3000 pixel image and it takes the brush 8 seconds to get from one corner to the other. CS4  never did that!

[Chris Cox]

lkemper - that is a completely different issue.   Most likely it's your video card not being up to using OpenGL drawing (esp. true of laptop graphics chipsets).

[lkemper]

Chris why can it keep up in CS4?

[_scott__]

CS5 is an entirely new code base than CS4. Although the two are the same app.. they are written in different manners. It's my understanding CS5 is Cocoa based and CS4 was still fairly Carbon based.

[lkemper]

SO the old code was more efficient?

[lkemper]

Do you know if the The NVIDIA GeForce GT 330M card in the new Macbook Pros can keep up?