Photoshop quitting during sleep...
 

There has been a few times now that I have walked away from my machine with Photoshop open (either in the background or the foreground) with unsaved files (not secessarily ones that I want to save - I am pretty good at always saving the important ones...) and the machine will eventually go to sleep as expected, but when I return, I find myself clicking on the PS icon in the dock only to realize (eventually) that I'm staring at the splash screen as it loads. For some reason, it likes to silently quit (occasinally) without any warning during sleep. There are no "Photoshop has unexpectedly quit, but everything else on your computer is really cool because I'm an advanced operating system with..." messages.

Has anyone else noticed this?

I'm running 10.2.3 on a TiBook 550, with PS 7.0...

Yes, I've also had that happen to me, although occasionally I will get the unexpected quit error message.

Not sure what causes it, though...

crash log?

~/Library/Logs/CrashReporter/photoshop...

Kern Protection Failure
Kern Ivalid Address

one or the other for all 50 crashes
I'm a non-geek...
What is that gibberish supposed to mean?

can't tell you unless we see more info.

copy/paste the most recent occurence of the two, i.e., the last entry in the crash log for each type, here.

(~Library/Logs/CrashReporter/Adobe Photoshop 7.0.crash.log was not recent...)

But this one is recent...

~Library/Logs/Adobe Photoshop 7.0.crash.log :

This is when there is a problem with your virtual memory I believe. Your computer is trying to access an invalid block of memory it thinks is virtual memory but really is not. I did a google search and found these articles, maybe they can help you out a bit.

http://www.gnu.org/software/hurd/gnu...oc/mach_5.html

http://www.gnu.org/software/hurd/gnu...oc/mach_9.html

Hope this helps out a bit.

more likely just a bad pointer referencing some invalid memory address. can't infer real or virtual memory routines, tho.

code fragment manager snarfEvents

is where things go south.

but i can't infer much from the log

OK, sorry :)
Here goes:

Date/Time: 2003-06-02 04:02:22 -0400
OS Version: 10.2.5 (Build 6L29)
Host: Shneur.local.

Command: Adobe Photoshop 7.0
PID: 1685

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000018

Thread 0 Crashed:
#0 0x0143fc14 in 0x143fc14
#1 0x01448ed8 in 0x1448ed8
#2 0x01449778 in 0x1449778
#3 0x013ddefc in 0x13ddefc
#4 0x00825ec4 in 0x825ec4
#5 0x00823964 in 0x823964
#6 0x00a4a688 in 0xa4a688
#7 0x00a3f044 in 0xa3f044
#8 0x00b744ec in 0xb744ec
#9 0x00b744ec in 0xb744ec
#10 0x00b7e960 in 0xb7e960
#11 0x003e5be0 in 0x3e5be0
#12 0x00b747dc in 0xb747dc
#13 0x00b81c18 in 0xb81c18
#14 0x00b81a78 in 0xb81a78
#15 0x00b07040 in 0xb07040
#16 0x00632970 in 0x632970
#17 0x00b04284 in 0xb04284
#18 0x00b021ec in 0xb021ec
#19 0x00b03d68 in 0xb03d68
#20 0x00b04468 in 0xb04468
#21 0x00b20354 in 0xb20354
#22 0x007d0d80 in 0x7d0d80
#23 0x007d1f8c in 0x7d1f8c
#24 0x0066fa20 in 0x66fa20
#25 0x006705ec in 0x6705ec
#26 0x00671018 in 0x671018
#27 0x003b64d8 in 0x3b64d8
#28 0x00668eb0 in 0x668eb0
#29 0x0b70a3f4 in 0xb70a3f4
#30 0x0b709878 in 0xb709878
#31 0x0b708f20 in 0xb708f20
#32 0x0b6fa130 in 0xb6fa130
#33 0x0b6f98dc in 0xb6f98dc
#34 0x00657a38 in 0x657a38
#35 0x003b6868 in 0x3b6868
#36 0x003b7b38 in 0x3b7b38
#37 0x004526f0 in 0x4526f0
#38 0x00b27894 in 0xb27894
#39 0x00b06350 in 0xb06350
#40 0x00affdf8 in 0xaffdf8
#41 0x00b0e098 in 0xb0e098
#42 0x00b0dab0 in 0xb0dab0
#43 0x00b06684 in 0xb06684
#44 0x00b06788 in 0xb06788
#45 0x00b04e68 in 0xb04e68
#46 0x0062db68 in 0x62db68
#47 0x00b07140 in 0xb07140
#48 0x00208a98 in 0x208a98
#49 0x00208b60 in 0x208b60

Thread 1:
#0 0x90042688 in semaphore_timedwait_signal_trap
#1 0x9003e8b4 in _pthread_cond_wait
#2 0x90232770 in TSWaitOnSemaphoreCommon
#3 0x9023b550 in TimerThread
#4 0x90020d48 in _pthread_body

PPC Thread State:
srr0: 0x0143fc14 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x01448ed8 ctr: 0x9022179c mq: 0x00000000
r0: 0x01448ed8 r1: 0xbfffc900 r2: 0x0184a000 r3: 0x00000000
r4: 0x00000000 r5: 0x00000000 r6: 0x00000000 r7: 0x00000000
r8: 0x00000000 r9: 0x1cb15285 r10: 0x00001ecf r11: 0x000066a0
r12: 0x003a1ecf r13: 0xbfffd888 r14: 0x01699824 r15: 0xbfffd5d4
r16: 0x01712cc8 r17: 0x00000001 r18: 0x00008002 r19: 0x003a1eca
r20: 0x00000000 r21: 0x00000001 r22: 0xbfffd5c4 r23: 0x01699818
r24: 0x01584c20 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000000 r30: 0x00000000 r31: 0x00000000

And again:

Date/Time: 2003-04-03 22:02:26 -0500
OS Version: 10.2.4 (Build 6I32)
Host: Shneur.local.

Command: Adobe Photoshop 7.0
PID: 799

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x323a3534

Thread 0 Crashed:
#0 0x323a3534 in 0x323a3534
#1 0x91ac2f90 in InternalDisplayChangedProc
#2 0x901632f0 in __CFRunLoopDoTimer
#3 0x90148e48 in __CFRunLoopRun
#4 0x90180fe4 in CFRunLoopRunSpecific
#5 0x969a3160 in RunCurrentEventLoopInMode
#6 0x969a3900 in GetNextEventMatchingMask
#7 0x969a7664 in WNEInternal
#8 0x969ad528 in WaitNextEvent
#9 0x00b035fc in 0xb035fc
#10 0x00630eb4 in 0x630eb4
#11 0x00b06ac8 in 0xb06ac8
#12 0x00b06750 in 0xb06750
#13 0x00b04e68 in 0xb04e68
#14 0x0062db68 in 0x62db68
#15 0x00b07140 in 0xb07140
#16 0x00208a98 in 0x208a98
#17 0x00208b60 in 0x208b60

Thread 1:
#0 0x90042688 in semaphore_timedwait_signal_trap
#1 0x9003e8b4 in _pthread_cond_wait
#2 0x90233384 in TSWaitOnSemaphoreCommon
#3 0x9023c170 in TimerThread
#4 0x90020d48 in _pthread_body

Thread 2:
#0 0x90073c48 in mach_msg_trap
#1 0x90005f90 in mach_msg
#2 0x0376106c in mouseTracker (main.c:283)
#3 0x90020d48 in _pthread_body

Thread 3:
#0 0x9003eaa8 in semaphore_wait_signal_trap
#1 0x9003e8c4 in _pthread_cond_wait
#2 0x9022ffd4 in MPWaitOnQueue
#3 0x16f20828 in MTBEWorker::WorkLoop(MTBEWorker*)
#4 0x16f1fa24 in MTBEWorkerStartMPTask
#5 0x9025e3dc in PrivateMPEntryPoint
#6 0x90020d48 in _pthread_body

Thread 4:
#0 0x9003eaa8 in semaphore_wait_signal_trap
#1 0x9003e8c4 in _pthread_cond_wait
#2 0x9022ffd4 in MPWaitOnQueue
#3 0x16f20828 in MTBEWorker::WorkLoop(MTBEWorker*)
#4 0x16f1fa24 in MTBEWorkerStartMPTask
#5 0x9025e3dc in PrivateMPEntryPoint
#6 0x90020d48 in _pthread_body

Thread 5:
#0 0x90073c48 in mach_msg_trap
#1 0x90005f90 in mach_msg
#2 0x90148b10 in __CFRunLoopRun
#3 0x90180fe4 in CFRunLoopRunSpecific
#4 0x94d9c1c0 in HALRunLoop::OwnThread(void*)
#5 0x94d911b0 in CAPThread::Entry(CAPThread*)
#6 0x90020d48 in _pthread_body

Thread 6:
#0 0x90042688 in semaphore_timedwait_signal_trap
#1 0x9003e8b4 in _pthread_cond_wait
#2 0x9022ffd4 in MPWaitOnQueue
#3 0x90736fc4 in TNodeSyncTask::SyncTaskProc(void*)
#4 0x9025e3dc in PrivateMPEntryPoint
#5 0x90020d48 in _pthread_body

PPC Thread State:
srr0: 0x323a3534 srr1: 0x4200f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x91ac1a14 ctr: 0x323a3537 mq: 0x00000000
r0: 0x00000001 r1: 0xbfffe400 r2: 0x4800424c r3: 0x17a54470
r4: 0x0000000a r5: 0xbfffe450 r6: 0x91e27cb0 r7: 0x00000000
r8: 0x00000000 r9: 0x040f542b r10: 0x040f83b0 r11: 0xa1a50df4
r12: 0x323a3537 r13: 0x00000000 r14: 0x00000000 r15: 0x00000001
r16: 0x00000001 r17: 0x00000000 r18: 0x24002280 r19: 0x00000000
r20: 0x00007fc7 r21: 0x00000000 r22: 0xa1a52b94 r23: 0x00047038
r24: 0x00000001 r25: 0x00000000 r26: 0x00000000 r27: 0x00000066
r28: 0xa0131674 r29: 0x0000000a r30: 0x0e55d1c0 r31: 0x91ac194c

Because of the dates, I'm not sure which crashes (if any of these) were from the sleep problem. If only I could figure out what on earth this log is talking about... :D

Photoshop and sleep
 

I've noticed the exact same problem, only I'm running Photoshop Elements 2.
It doesn't happen everytime, and doesn't seem to occur when I actually put my machine to sleep, only when the energy saver settings kick in.

Rob.

I can't remember if it occurs for me when I sleep it, or when the Energy Saver kicks in, but I suspect that it's the latter too.

Have you added any new after market ram to your apple lately? I would take out all the extra ram in your system and just use the factory ram and see what happens.

nope. All factory ram here.

Dodgy RAM
 

I've got 512MB single DIMM factory fitted. The user accessible slot is, and always has been, empty. So I guess that rules out that possibility.

Not sure when this started happening, but I've been using Photoshop Elements 2.0 since Mac OS X 10.2.2

Pretty sure everytime its happened I've had images minimized to the dock, can't remember if thats true for every occassion though. Just thought it might be worth mentioning.

Re: Dodgy RAM
 

Rob check your system log right after it happens.

It did it again!
 

Sorry about the delay, tried a few times to recreate the problem but no joy...
until just before...

I'd tried opening a few files, minimizing some to dock and leaving it to sleep, but each time I woke it up-everything was fine.

But just before, I opened up a few old photos and started editing one of them, got called away and thats when it happened. It was weird, not like previous times-where I'd wake up my iMac and Photoshop Elements 2.0 would be gone from my screen(no error messages, graphical glitches etc) This time it woke up and everything seemed normal. That was until I closed the image I had been editing. (which I did almost immediately) I answered the save dialogue, and then in quick succession each image popped up from the dock and closed. Next thing I knew the palettes had gone too and 'Elements was no longer running. No Errors, it was just as if I had quit the application.

Now I don't know about Terminal and the UNIX side of things, but I did check the logs folder in my user library. The only crash log for 'Elements dated back to Mac OS X 10.2.4. However the log opened in Console and I noticed this in the console window:

*** malloc[356]: Deallocation of a pointer not malloced: 0x30d0000; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
*** malloc[356]: Deallocation of a pointer not malloced: 0x30d1000; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug

Haven't got a clue what that means but I remember an earlier post about memory allocation going wrong, and it wrang a bell. Does this make any sense to anyone?

Rob.

crash log
 

Did you look under the CrashReporter sub-folder ? The logs used to go into the ~/Library/Logs folder but now they go into the CrashReporter sub-folder of ~/Library/Logs

Sorry, should have mentioned that. Yes, the out of date log I mentioned is in the crash reporter sub-folder. There are no loose (visible at least) files in my actual logs folder. Like I said earlier, there are no error messages, (and it appears no logs) when it happens. It just seems to disappear without a trace when (coming out of?) a deep sleep.

Just noticed, I'm now a Triple-A player! Not sure what that means, but it sounds better than "Prospect". If it goes on number of posts, then its a bit unfair if you think about it. Most of my posts have been in response to other people's questions, where I have tried to help if I can (whether I was actually any help is debatable of course!)
But someone who asks loads of questions (without bothering looking up previous hints in some cases) could rack up a big number of posts easily.

Sorry that was a bit off topic.

Anyway, back to the problem in hand...
Not exactly scientific, but each time I have encountered the "Photoshop (Elements) quit on (waking from?) sleep" problem was under the following conditions:
Sleep activated by Energy Saver
Multiple images opened
Images minimised to dock
Editing in progress when sleep occurred
(ie multiple layers, cut & paste, actions listed in history palette)

No apparent error dialogues or log entries-it just disappears!

Can somebody else check to see if they can reproduce the problem, and possibly eliminate or confirm any of the above?

Thanks

Rob.

You are not using frontier, or have it installed on your system do you? Also you should type this in the console right after it locks in sleep.

Also after doing a bit of google searching these links should help you out a bit also:

http://www.cbmamiga.demon.co.uk/mpatrol/

malloc is the C function to allocate memory, so something out there is trying to deallocate memory that isn't there it sounds like. That means its trying to remove memory that is unallocated. Its more than likely a software related problem. Whats the last thing you did to your system upgrade/install wise? I saw a few other posts on different sites that had this problem with frontier and fink. You have either of those 2 installed? Do you have the developers tools installed?

Hi, followed that link you posted, nice to see Amigas are still going! Although the system requirements wanted an '040 and Work bench 3.1 thats a high spec Amiga! Got the rough gist of what it was on about, a problem with virtual memory. Which did make me think, has anybody else experiencing this problem cranked up the memory usage in Photoshop (Elements) prefs? I can't remember what the default value is, but I've raised it to 75% of available RAM (calculated dynamically I believe?) Could this be related?

As for Frontier, wasn't that the sequel to Elite? (Sorry-still remembering my Amiga) and from what I've picked up on the site, Fink is something to do with UNIX that causes a lot of people headaches. Don't think I've ever even inserted the Developer Tools CD. Basically the limit of my System editing is occasionally changing the Desktop pic. I have no third party add-ons, scripts, haxies etc. So I guess my System is pretty (not sure if this is right) vanilla?

I've copied and pasted that piece of code into Stickies so its handy next time it happens. Thanks for that.

Rob.

Interesting... I have set mine to 92% (of 1GB). I do quite a bit of work on large 500+MB files... I wonder if this is a clue... Regardless, I know that PS has vanished during sleep while I was working on a few web projects - those files are seldom over 5MB, not quite pushing any limits. ;)

hisbonenus, how about you? What's your memory allocation?

What about scratch disks???
 

Do you have a scratch disk? I am not a designer, but I have worked for a bunch. I recently configured a ibook 900Mhz for this photographer/website designer. She had some weird production fashion photos she was selling to some magazine company. The magazine company had all these preferences you had to follow to submit a picture (like size, color, layers, lighting, etc etc). Well she was having problems with photoshop, she had 512 mb of ram. I ended up making a scratch disk partition for pshop, and it really helped the performance of the problem. I gave pshop a whole gig of scratch disk space, and she has not been back by to complain or make me fix her ibook again. Maybe this might help some of you, I don't know.

Re: What about scratch disks???
 

Dedicating a partition to PS would definitly speed things up because there would be no fragmentation, as the only files being written to the partition would be the temporary 'swap disk' files which are deleted upon ending the PS session. It would also help with switching between apps as PS needs to re-optimize the info in RAM after switching to other apps which take some of the memory PS was using. it does this by heavily accessing the 'swap disk' file (when switching back to PS) and assigning new info to be stored in the now smaller amount of RAM. I'm not sure if that would help. It could. I can't try it, but if anyone else has the means, I'd be interested in hearing what happens.

Yeah, you would have to repartition your whole HD, and would effetively lose all data. Unless there is a partition magicesque program out there for the mac. I have no idea if there is one.

Yeh, guess that would make a lot of sense, using a dedicated scratch disk.
All the old Bondi iMacs in Uni were set up like that. But I'm only a light user at the moment (havin to take some time out from uni-long story) All I've used 'Elements for is occassionally cropping a few approx 1MB jpgs from my digital camera. Not exactly taxing stuff. Thats why I've only experienced the problem a few times, because I've barely used it. Luckily I've never lost anything important, but it must be a real worry for people who use Photoshop daily.
In that situation, the obvious solution would be just have the display set to sleep.

Rob.