Photoshop CS4 11.0.1 – crash upon save, leaves small sized corrupt PSD file

[Martin_B...@adobeforums.com]

Hi!

I've just updated our retouchers Photoshop CS4 to 11.0.1 but one of the issues we had with 11.0.0 remains. The problem doesn't happen that often, but since the result is an unusable .PSD file it's pretty nasty...

Sometimes when saving Photoshop crashes and the .PSD that was to be saved becomes a small (68 KB in the last example) and unusable.

The hardware/software we have:

Mac Pro 2.66 GHz (some with 5 GB RAM and some with 9 GB RAM)
Mac OS X 10.5.6
Photoshop CS4 Standard (updated to 11.0.1)
People work on server volumes shared via AFP. I've heard saving over the network isn't supported, but there's no other way, plus this issue never happened in CS3 so...

Any ideas on what can be done?
Below is the latest crash log:

Process: Adobe Photoshop CS4 [41265]
Path: /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/MacOS/Adobe Photoshop CS4
Identifier: com.adobe.Photoshop
Version: 11.0.1 (11.0.1x20090216 [20090216.r.522 2009/02/16:17:00:00 cutoff; r branch]) (11.0.1)
Code Type: X86 (Native)
Parent Process: launchd [84]

Date/Time: 2009-03-24 11:04:07.914 +0100
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000008
Crashed Thread: 0

Thread 0 Crashed:
0 com.adobe.Photoshop 0x00748248 0x1000 + 7631432
1 com.adobe.Photoshop 0x004d962d 0x1000 + 5080621
2 com.adobe.Photoshop 0x004dda2f 0x1000 + 5098031
3 com.adobe.Photoshop 0x004dedba 0x1000 + 5103034
4 com.adobe.Photoshop 0x004a6a58 0x1000 + 4872792
5 com.adobe.Photoshop 0x000821ad 0x1000 + 528813
6 com.adobe.Photoshop 0x00082bdb 0x1000 + 531419
7 com.adobe.Photoshop 0x00acb564 0x1000 + 11314532
8 com.adobe.Photoshop 0x004a5f6e 0x1000 + 4869998
9 com.adobe.Photoshop 0x00077f9e 0x1000 + 487326
10 com.adobe.Photoshop 0x0006b9ed 0x1000 + 436717
11 com.adobe.Photoshop 0x00069906 0x1000 + 428294
12 com.adobe.Photoshop 0x00063d65 0x1000 + 404837
13 com.adobe.Photoshop 0x00063ed3 0x1000 + 405203
14 com.adobe.Photoshop 0x0006222f 0x1000 + 397871
15 com.adobe.Photoshop 0x002206aa 0x1000 + 2225834
16 com.adobe.Photoshop 0x00220736 0x1000 + 2225974
17 com.adobe.Photoshop 0x00003912 0x1000 + 10514
18 com.adobe.Photoshop 0x00003839 0x1000 + 10297

Thread 1:
0 libSystem.B.dylib 0x92893906 kevent + 10
1 libSystem.B.dylib 0x92894095 _pthread_start + 321
2 libSystem.B.dylib 0x92893f52 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x9286320e semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x92895206 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x928da539 pthread_cond_wait + 48
3 com.adobe.amt.services 0x04da4552 AMTConditionLock::LockWhenCondition(int) + 46
4 com.adobe.amt.services 0x04d9f995 _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 115
5 com.adobe.amt.services 0x04da45b0 AMTThread::Worker(void*) + 20
6 libSystem.B.dylib 0x92894095 _pthread_start + 321
7 libSystem.B.dylib 0x92893f52 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x9286a3ae __semwait_signal + 10
1 libSystem.B.dylib 0x92894d0d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x95affb32 glvmDoWork + 162
3 libSystem.B.dylib 0x92894095 _pthread_start + 321
4 libSystem.B.dylib 0x92893f52 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x9286321a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x9237449b MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1

[Martin_B...@adobeforums.com]

Oh, I see the crash log didn't fit.

Here it is in its entirety:
<http://home.mac.se/star-affinity/photoshop_crash.html>

[Chri...@adobeforums.com]

Make sure you send the crash reports to Adobe (via the prompt on crash, not here).

[Martin_B...@adobeforums.com]

Hi Chris,

I've told the users to do that, so I hope they do...
If there's anything I can do to help (more crash logs or whatever) just let me know.

Thanks!

[Ramón_G_Castañeda@adobeforums.com]

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.

[Ramón_G_Castañeda@adobeforums.com]

Still, this is the first time I hear about a crash when saving to a server, not just damaged files.

[Chri...@adobeforums.com]

Ramon - yeah, that isn't common. And the other crashes on save that we're tracking all crash in Apple code, not inside Photoshop itself.

[Ramón_G_Castañeda@adobeforums.com]

And the other crashes on save that we're tracking all crash in Apple code,

Hopefully all in Leopard?

[Martin_B...@adobeforums.com]

So the crash I reported above wasn't in Apple code?

Thanks for your input, guys!

[Martin_B...@adobeforums.com]

Chris,

Is there a poin to send the crash logs to Apple, or are you guys communicating with them already?

[Buko]

If the Apple crash log pops up send it to Apple. If Adobe and Apple pop up send to both.

[Chri...@adobeforums.com]

When you send in the crash logs, 99% of them go straight to Adobe.
Those that go to Apple eventually come back to Adobe.
And we try to find patterns in the crashes and fix those we can (and report Apple's bugs to them).