The application photoshop quit enexpectedly. Happens when i close the program.

Question

Hello,<br /><br />Some help please. Using photoshop CS3. Great program no problems with it. Just an irritating notice everytime i exit the program. The Apple error reporting dialog comes up. I have an iMac 24", with 4 gb ram, ATI Radeon 2600 graphics card, the 2.4 ghz dual core model, running Mac OSX 10.5.1 . The report reads as follows from my console program.<br /><br />01/02/09 3:57:59 PM Bridge CS3[222] *** -[NSConditionLock dealloc]: lock (<NSConditionLock: 0x18563460> '(null)') deallocated while still in use <br />01/02/09 3:57:59 PM Bridge CS3[222] *** Break on _NSLockError() to debug. <br />01/02/09 3:57:59 PM Bridge CS3[222] *** -[NSLock unlock]: lock (<NSLock: 0x185633e0> '(null)') unlocked when not locked <br />01/02/09 3:57:59 PM Bridge CS3[222] *** Break on _NSLockError() to debug. <br />01/02/09 3:57:59 PM Bridge CS3[222] *** -[NSLock unlock]: lock (<NSLock: 0x18564030> '(null)') unlocked when not locked <br />01/02/09 3:57:59 PM Bridge CS3[222] *** Break on _NSLockError() to debug. <br />01/02/09 3:57:59 PM Bridge CS3[222] *** -[NSLock unlock]: lock (<NSLock: 0x18563f90> '(null)') unlocked when not locked <br />01/02/09 3:57:59 PM Bridge CS3[222] *** Break on _NSLockError() to debug. <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** -[NSConditionLock dealloc]: lock (<NSConditionLock: 0x2d4a690> '(null)') deallocated while still in use <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** Break on _NSLockError() to debug. <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** -[NSLock unlock]: lock (<NSLock: 0x2d4a600> '(null)') unlocked when not locked <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** Break on _NSLockError() to debug. <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** -[NSLock unlock]: lock (<NSLock: 0x178dfdd0> '(null)') unlocked when not locked <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** Break on _NSLockError() to debug. <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** -[NSLock unlock]: lock (<NSLock: 0x178dfd90> '(null)') unlocked when not locked <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] *** Break on _NSLockError() to debug. <br />01/02/09 3:58:09 PM Adobe Photoshop CS3[178] Internal error unloading bundle CFBundle 0x1ae5f290 </Library/Image Capture/TWAIN Data Sources/EPSON CX7300_CX7400_DX7400.ds> (bundle, loaded) <br />01/02/09 3:58:09 PM [0x0-0x1d01d].com.adobe.Photoshop[178] Adobe Photoshop CS3(178,0xa0358720) malloc: *** error for object 0x1e714930: Non-aligned pointer being freed (2) <br />01/02/09 3:58:09 PM [0x0-0x1d01d].com.adobe.Photoshop[178] *** set a breakpoint in malloc_error_break to debug <br />01/02/09 3:58:22 PM com.apple.launchd[75] ([0x0-0x1d01d].com.adobe.Photoshop[178]) Exited abnormally: Segmentation fault <br /><br />Does anybody know what this means. I am irritated that $700 program doesn't come with support and closes like this. I thank you for any time you spend reading this.<br /><br />Thanks,<br /><br />Nick

Answer 1

I still advocate Repairing Permissions (with Apple's Disk Utility) before AND after any system update or upgrade, as well as before AND after installing any software that requires an installer that asks for your password.
I have seen software installations go sour because the installer did not find everything as and where it should be.
I have also seen software installations go bad because the installer did not clean up after itself properly and did not leave everything as and where it should be.
This is just my own personal opinion and practice based on my own observations. Others may disagree and that's OK. I can only base my routines and my advice to others on my own experience and conclusion. I don't pretend to know why others believe otherwise.
Repairing Permissions after the fact (i. e. not immediately before and after an install) may NOT help. Try it anyway, though.
====
Additionally, if your machine does not run 24/7 so that it runs the daily, weekly and monthly Cron Scripts in the middle of the night as intended by Apple, run Cocktail (shareware) as well.
Cron Scripts are maintenance routines designed by Apple to run on a daily, weekly and monthly basis in the middle of the night.
If you don't run them, you WILL run into trouble, sooner rather than later.
Here's an excerpt from the Apple tech doc http://docs.info.apple.com/article.html?artnum=107388
Mac OS X performs background maintenance tasks at certain times if the computer is not in sleep mode. If your computer is shut down or in sleep at the designated times, the maintenance does not occur. In that case, you may want or need to run these manually.
Mac OS X periodically runs background tasks that, in part, remove system files that are no longer needed. This includes purging older information from log files or deleting certain temporary items. These tasks do not run if the computer is shut down or in sleep mode. If the tasks do not run, it is possible that certain log files (such as system.log) may become very large.
Also, from: http://docs.info.apple.com/article.html?artnum=106978
The disk activity generated by find is a normal part of file system maintenance, used for tasks such as removing invisible temporary files that are used by the system. It is scheduled to occur early in the morning at 03:15 everyday, 04:30 on Saturdays, and 05:30 on the first day of each month.
NOTE:
There have been comments to the effect that Apple "fixed" this in 10.4.2 and later versions of the OS, but I have not been able to verify this to my satisfaction. The reference in the 10.4.2 release notes are far from explicit on this subject.
= = =
If you have DiskWarrior, run it regularly too.