Participant

質問

Mac Photoshop CS4 stalls – force quit quits the app, but it remains active in the Dock

Forum|Forum|16 years ago
May 20, 2009
返信数 13.
26809 ビュー

Our retouch department is having some issues in Photoshop CS4 11.0.1.

One of the problems is that Photoshop suddenly just stalls while working (beach ball spins) and it doesn't stop.

Below are four different samples of Photoshop when in the stalled state:

http://home.mac.se/star-affinity/sample_of_photoshop.txt

http://home.mac.se/star-affinity/sample_of_photoshop_2.txt

http://home.mac.se/star-affinity/sample_of_photoshop_3.txt

http://home.mac.se/star-affinity/sample_of_photoshop_4.txt

http://home.mac.se/star-affinity/sample_of_photoshop_5.txt

When this stall happens, if one tries to force quit Photoshop it ”goes away” from the Activity Monitor, but the icon in the Dock remains active as if the application is still running. After some few minutes (around five maybe) it finally ”gets quit” in the Dock too so it can be relaunched.

Any ideas on this?

We run the first version of Mac Pro (2.66 GHz) with the ATI X1900 graphics card.

Some run 10.5.6 but some have started to move to 10.5.7.

Some have 5 GB RAM and some have 9 GB RAM.

All samples above are from a machine running 10.5.6, but I've heard the stall also happened on a 10.5.7 machine.

このトピックへの返信は締め切られました。

Y

yepexactly

Known Participant

This has been happening for years

Adobe applications take minutes to quit, refuse to quit, on "Force Quit" they will become inaccessible but they won't show as inactive. Meaning you can't access them, but they still show in the dock as though they are launched and you have to restart to be able to launch them again.

The worst are Adobe Acrobat and InDesign followed by Photoshop, Illustrator some and Bridge is typically pretty good. It's a much more common complaint than you see on the boards here. It has been and is ongoing. I have encountered it on various Mac platforms and with various versions of CS.

Adobe will claim it is a system error or an install error, etc. . . The problem is that it is ONLY Adobe applications that I have every encountered this with. And it is always the SAME Adobe applications. I do find that it is even worse when the computer is connected to a server. This is an Adobe problem and they don't seem to ever truly address it.

I am a huge fan of all of the Adobe products, but this is and has been a problem in the applications and I never see any discussion from Adobe about actually trying to figure it out. I see all these "fixes" which are really attempts to backdoor the inherent problem in the software itself.

Get it fixed.

Tai_Lao

Inspiring

I've never encountered that problem, ever.

It would be helpful if you provide detailed information about your setup and the precise steps needed to reproduce your issue.

Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:

http://forums.adobe.com/thread/419981?tstart=0

Thanks!

Y

yepexactly

Known Participant

It’s in the forums. I’m not really going to try and replicate all the steps and go through my history of installs, system configurations etc. . . , it happens and it happens a lot. Adobe applications take forever to quit and have for some years now. You have posting going back before 2004 about the programs not quitting. There seems to be plenty of documentation.

A

Anonymous

Me too!

If you're running PS CS4 on a mac older than the latest model, I believe you will find that it's the video card driver. I just went through a long series of diagnostics with Adobe. Here's the steps you can take to dicsover the cause:

http://kb2.adobe.com/cps/404/kb404895.html

I did them all and everything points to #6. You'll also most likely discover that there is no way to upgrade your driver to a compatable version. There is no upgrade for my iMac. According to what I was told, if there was an upgrade it would have come along automatically with any other upgrades for my mac system (which I apply regularly). The NVIDIA website does not provide upgrades for macs in general even though they supply the video cards to Apple. I imagine I could buy a new video card altogether, but haven't gone that far yet (and don't know for sure if I will).

If you're having trouble in PS CS4 make sure that OpenGL Drawing is disabled in the preferences (in the Perfomance panel). I got better performance (no permanent hangs and those that happen end after several seconds) after I deselected that. Be sure to check out the two links at the bottom of section #6 in the document above as they discuss the OpenGL in more detail (and it's incompatability with many drivers).

When I run PS CS4 on my brand new iMac at home (bought this year) PS CS4 works beautifully.

Although the "permanent hang" has been eliminated, now I get a strange error message when I try to open a file...."PS cannot complete your request"...and can't continue to open the file because the error message won't go away. Oh well that's a story for another day and another Adobe Support Request and It's back to CS3 for me for the time being.

Good luck everyone.

iMac # 2.33 GHZ Intel Core2 Duo # 3GB Ram # 667MHz DDR2 SDRAM

NVIDIA GeForce 7600 GT

MAC OS 10.5.7

Design Premium CS4

K

kkrimmer1

Participant

Cmd-Opt-Esc to Force quit CS4... Photoshop USED to be the most stable reliable programs, now it works great when it works...

RE: Brent's solution
Command+Option+Shift keys as I launched CS4

What I found in the system info was
Plug-ins that failed to load:
Adjusted Refresh NO VERSION

I did a Spotlight search for Adjusted Refresh, found two copies, deleted both. We'll see if anything changes.

-

-_JM_-

Known Participant

star-

I'm just being curious

were all of your computers, clean installs (new computers with new software loaded) and not migrations from older computers with older CS suites?

thanks

j

A

Anonymous

The iMac was a clean install (since it was the first Mac), and the

MacBook Pro I migrated from the PC, but ended up doing a clean install

of Adobe after working from the transferred apps - though it didn't

make a difference.

-ash

-

-_JM_-

Known Participant

thanks for the speedy reply!

I'm trying to clean house and was wondering if legacy suite files were problems such as older Version Cues etc...... you've ruled that out.

next up.....

I see in the activity monitor that AdobeCrashDaemon runs when I run any of the suite apps. I guess this is normal?

and I see that in the System log within the Console that I have repeated messages " unknown SIGSEGV code O"

which led me to googling the universe and found this conversation.....

http://discussions.apple.com/thread.jspa?threadID=1548818&start=15&tstart=0

and this technote-

http://kb2.adobe.com/cps/408/kb408562.html

with this entry-

"These SIGSEGV signal messages have been determined to be sent from debugging code that was not disabled. Note that all Mac users of CS4 applications, or Acrobat/Reader 9.0 would see these messages in their system.log, so any crashes are merely coincidental. However, if your crashes are related to a problem with the FLEXnet licensing server, this solution may also fix that, as it causes many of it's files to be refreshed, which could remove corruption.

This issue can be resolved by downloading and running the updated Adobe Licensing Repair Tool:
http://www.adobe.com/support/contact/licensing.html

Note: If you have previously downloaded this utility, your browser cache may contain the previous version. The correct version will mount a disk titled, "LicenseRecovery11.5.0.9". If the disk image you mount does not mount with that name, clear your browser cache and download from the link again.

Matthew Laun

Adobe Technical Response Team"

I haven't tried the licensing fix yet..... too much work today and I'm a little worried that I will end up with licensing problems with the suite, which would be somewhat disastrous.

oh well..... I'll keep staring at my computer.... I mean working : )

A

Anonymous

I'm having the same problem - brand new MBPro, running files off of the server (after this forced restart - 4th one this afternoon - I'll try copying/pasting the files...ugh) I've tried right-click force quitting from the dock, relaunching Finder, turned off OpenGL or w/e in prefs... no luck.

I also agree that this is of course totally unacceptable. I am losing soo much time on this, and as all of you, we have deadlines to meet...and although I'm working late nights already, I don't want it to be because of some glitch in the software (or wherever it is). It doesn't do this on the new (month old) iMac in the office...

Keeping my eyes on this thread and hoping a solution comes up.

A

Anonymous

Copy/Paste works - but I should also mention Bridge is doing the same thing, though I don't know the cause since it obviously isn't save... So now I'm force-shutting-down because of that.

-

-_JM_-

Known Participant

Hi Star

I guess we have 2 things going on, the crashing/stall and the delay force quit.

I'm experiencing the delayed PS force quit problem but I'm working on local drives, so is it possible that irregardless of the network situation the force quit delay is a problem with how PS rebounds from a problem? To restate, is the reason for the crash related to the force quit delay or independent?

Most often I am getting a crash ( not a freeze/stall ), and the Apple crash reporter appears, but there is still a delay in being able to restart PS.

Are you only experiencing "stalls" or are you also seeing crashes(application quits)?

Do you see the crash report after the force quit and then wait or does PS finally quit just after the crash report is visible? is it Apple or Adobe crash reporter?

I can certainly understand that working over a network might introduce other potential problems but the end result of the delayed force quit is a common symptom.

general questions:

Are there any applications that are tethered to PS such as other suite apps, that would cause PS to delay force quit?

Is there anything that I can view in the crash report that would help uncover the problem?

what makes PS different from other applications that don't have a problem with force quit? ( if this is related to the OS and not Adobe's problem, what is PS doing that other applications aren't, VM? )

what version OS, PS and is everyone with this problem using a version of the suite? (mine - 10.5.7 CS4 Suite, PS extended)

A

antiisthefuture

Participant

I have the same exact problem. Multiple times a day. It doesn't matter if i'm saving a file, closing a file, or anything else. Does this happen to anyone working on local files? I am constantly working off files on the server and I'm not sure if that is the problem or not.

This occasually happend in CS3 when working with smart objects but if I just waited for 10 mins or so Photoshop would unfreeze.

Ramón G Castañeda

Inspiring

antiisthefuture wrote:
…I am constantly working off files on the server and I'm not sure if that is the problem or not…

This is the boilerplate text I use in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):

If you are opening files over a network or saving them to a network server, please cease and desist immediately in the event you are currently experiencing problems with one or more files. Working across a network is not supported.

See:

http://www.adobe.com/support/techdocs/322391.html

Copy the CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.

Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work. It should.

Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.

If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.

When problems arise, a lot of valuable work can be lost.

S

star-affinity作成者

Participant

I fully understand that there will be problems if the network is not performing as it should.

The question is if there are any network that are working ”as it should” in conjunction with Photoshop? Anyone?

The IT equipment at the office where I (and our retouchers that are having problems) work was installed in the end/beginning of 2007/2008.

The sever is an almost 80 kilos Sun server running the Solaris Operating System and has the ZFS filesystem. For AFP file sharing we also run Helios software on the Sun server. The RAID where the PSD files are stored is also from Sun. The network switches are ”enterprise class” equipment from Cisco.

What I'm trying to say is that it's pretty heavy IT equipment involved here.

In total there are maximum 14 people from retouch working on the server at the same time and we also have several different ”network segments” to even out the traffic.

If it *should* work to work across the network I'm really curious about what in the setup above could be causing the problem.

Ramón G Castañeda

Inspiring

Since Photoshop 11.0.1 does not crash on my officially unsupported, five-years-old and modest Dual MDD G4, I'll just list what I do differently with no further comment and no claim that any of this will make Photoshop CS4 more stable on other machines.

• I have my Photoshop preferences set to NOT export the clipboard.

• I manage fonts with FAP.

• I run Tiger 10.4.11, with Dashboard and Spotlight permanently disabled.

• Dual bootable, DP MDD 1.25GHz G4 (2004), maxed out at 2GB of RAM, both Spotlight and Dashboard disabled, Photoshop primary scratch disk on dedicated 160GB internal drive, at least 100GB available on each of the four internal drives, up to 300GB on some. Counting external FW drives just over 1TB of drive space available. nVidia GeForce 7800 GS 425MHz 256 MB "mutant" flashed graphics display card. Processor napping enabled through CHUD 3.5.2.

C

Craig F

Known Participant

Same problem here. Photoshop CS4 crashes (4 or more times a day if working with Smart Objects) and then it will not force quit. The whole quit and relaunch process takes 5-10 minutes. Nothing is running in the Activity Monitor. I would have gone back to CS3 last year if I could. CS4 is embarrassing for me to run when I'm with clients. This happens both of my macs. If it's an Apple problem someone from Adobe should get with them. This is unacceptable. Sorry Adobe but you dropped the ball on this one. I do not recommend that anyone on a mac upgrade to CS4. The new features are nice but you have to be able to work.

I'm not expecting an answer. This is just a rant. Oh - I have to stop writing now so I can restart AGAIN!!

-

-_JM_-

Known Participant

Hi Craig

>when I'm with clients.

I hate to state the obvious, but the problem is probably having clients in the studio.

Unfortunately I don't know if there is anyway to fix it. If you try to remove the clients it often causes other problems.

: )

C

Craig F

Known Participant

Yes. The crashing IS less worrisome than lack of clients! Ha.

W

Wilczak

Participant

I have experienced this issue. Force quit does not seem to work nor does an obvious process show up in the Activity Monitor application. I resolved the icon still showing photoshop as open in the dock by relaunching the Finder in OS X. This then allows you to restart PS without a restart.

K

KiersM

Participating Frequently

Hi All

I've been having this problem on a brand new mid-09 Macbook Pro.

One thing I did find today when it happened was:

- I repeatedly tried force quit, and like you all said, the windows closed, and the process was removed from the activity monitor, but the dock still showed the dot, and the force quit dialog still showed photoshop (not Responding) - although the "not Responding" went after a few minutes.

- I then Secondary clicked the icon in the dock and selected "Force Quit" from there, and hey presto, the dot disappeared and I could restart the app

I don't know if I just hadn't had as severe a stall as you all, or not, so I'll keep trying it next time it happens - Part of me refuses to believe that simply force quitting via the dock icon is a workaround, but give it a try and let me know if helps in your situations too.

Cheers

Kieran

-

-_JM_-

Known Participant

Hi Kiernan

I can report that this isn't effective in the situations where I've experienced it, force quitting from the dock has no effect for me.

here are the questions that I would have:

Does the AdobeCrashReporter send data to the Apple Crash Reporter, or is the AdobeCrashReporter independent and the Apple CR collects it's own set of info?

If AdobeCrashReporter were disabled ( I've asked and the end-user apparently can't do this ) would it fix the stalled force quit.

Why does this stall only effect PS? ( or has anyone heard of other apps that experience the same problem? )

---

the irony is that relatively few people are complaining about the crashing, but instead the problem is something that should be part of the remedy.

j

Chris Cox

Legend

Thanks Chris

Has Adobe determined that this is an Apple only problem?

and should we be reporting this directly to Apple or are they aware of the problem?

is the following the best link for an Apple bug report and is there anything that we should include in our description to help pinpoint the issue?

http://developer.apple.com/bugreporter/bugrptform.html

regards

j

I really don't know.

Whenever we hear about crash reporter taking forever, it usually just takes 5-10 minutes because of some issue on the user's machine.

I haven't heard enough reports of problems to file a bug with Apple.

But you can file a bug if you wish.

さらに返信を表示

サインアップ

ソーシャルログイン

コミュニティへログイン

ソーシャルログイン

ファイルをウイルススキャンする。

このファイルはダウンロードできません