Adobe Community: Strange system log error from Photoshop CS4

Currently Being Moderated

40. Dan_Perfect,

Feb 25, 2010 2:03 AM in reply to MuggeGHQ

Report

HI,

Did anyone actually come to a conclusion about what this error is? I've been driving myself nuts with trying to troubleshoot this, and not figured it out..

I'm getting the same error as the OP,

25/02/2010 09:48:03 Adobe Photoshop CS4[255] Adobe Photoshop CS4(255,0xa0012500) malloc: *** mmap(size=17002496) failed (error code=12)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

Goes on endlessly, and eventually CS4 hangs, often during a save or open operation.

I have tried lots of re-installs, isolating memory etc. 10.6.2, 12GB RAM, 2 x 2.26GHz Quad Core.

I don't have any 3rd party plugins, and it happens for me whichever clean installed HD I boot off.

Im working with reasonably large files, up to a gig, but I keep an eye on the memory allocation, and I always have plenty of headroom..

Some help on this would be appreciated!

Thanks

Dan

|

Mark as:

Currently Being Moderated

41. MuggeGHQ,

Feb 25, 2010 11:04 AM in reply to Dan_Perfect

Report

Hi Dan_Perfect

I still have the problem

And also 12GB of Ram. I never tried change the amount of ram back to something else.

Before i installed the extra memory. There was no problems ???

Strange really.

|

Mark as:

Currently Being Moderated

42. Wade_Zimmerman,

Feb 25, 2010 11:48 AM in reply to MuggeGHQ

Report

It was suggested it might be hardware related have you investigated did you remove the RAM you installed?

It could be poorly installed not properly seated or it can be bad RAM. Why not find out?

|

Mark as:

Currently Being Moderated

43. Chris Cox,

Feb 25, 2010 8:25 PM in reply to Dan_Perfect

Report

At this point, I'm reasonably sure that the messages are an OS thing.

And I'm pretty sure you can just ignore them. They are status information, not actual errors. (someone was just overzealous about reporting allocation failures)

|

Mark as:

Currently Being Moderated

44. MuggeGHQ,

Feb 26, 2010 12:17 PM in reply to MuggeGHQ

Report

Hi both, and thx for all your help and suggestions

Yea. i think your right about you can ignore the error.

The only thing that bothers me are after you have spend a lot of time on a picture and you want to safe it.

Then this happen. But i get around this by just saving the picture to the desktop and then move it to the

right folder after. Then restart Photoshop. Photoshop needs to restart everytime you get this error because

the error message dosent go away before photoshop is restarted.

I learned to live with it for now and i think it is a memory question.

It only happen when i have 12GB or 16GB installed. Not 10GB or 8, 4 or something. 12GB and 16GB ???

And it wasn't there when i had 10.5.4 or 5 installed, it came after i updated my system to 10.5.8. Weird.

I did tried to swop the ram blocks around and also ran some test on them. All are good.

It is a combination of exactly the amount of memory installed funny enough. Thats what i think anyway.

But i'm not a technition, so what do i know its just a feeling.

Again. Thx for all the replays here and i will follow the tread and see if something comes op one day.

Photographer

Erik DK

|

Mark as:

Currently Being Moderated

45. Chris Cox,

Mar 1, 2010 6:42 PM in reply to MuggeGHQ

Report

Except that it isn't an error, and the message has no effect on Photoshop's operation....

What happens is that the OS says "there is 4 meg available to allocate", and Photoshop thinks it can safely allocate 2 Meg. But that allocation fails because the address space is fragmented. Then Photoshop backs off the allocation to 1 Meg and tries again. But when the 2 Meg allocation failed, the OS printed a message to the console (probably debugging code mistakenly left in the OS). Photoshop keeps working, the OS keeps working - nothing should fail. It's just a warning message from the OS code that really doesn't mean anything.

|

Mark as:

Currently Being Moderated

46. MuggeGHQ,

Mar 3, 2010 8:17 PM in reply to Chris Cox

Report

yes, it is just a message but not quite.

Everytime i get the error i have to restart photoshop before it works normal again.

If the error message comes ones. It dosent go away before a restart and i cant save

any pictures to my main picture drives before i restart PS.

So its not just a error message and nothing else. That would have been alright.

But woulden it be possible to make a PS update that fix this error message ?

|

Mark as:

Currently Being Moderated

47. Chris Cox,

Mar 6, 2010 2:37 PM in reply to MuggeGHQ

Report

Again, it is not an error message - that message is normal, and just the OS reporting more stuff than it should to the console. Other users have that message come up in the console all the time - with no ill effects. If Photoshop fails to allocate memory, it just frees up some memory and tries again until it succeeds. Again, this happens all the time.

Something else is doing on that prevents you from saving, something that might be related to the allocation errors, but probably not. If a third party plugin or driver is leaking memory, or messing up the OS memory system -- that could cause problems down the road and might cause allocation error messages.

But while you are seeing problems saving files, other users are not.

Adobe hasn't seen such a problem.

And we can't fix what we've never seen (and have no idea what might be causing it).

So, calm down and let's see if we can figure out what is happening to your system, and why it only happens to you.

Do you use any third party plugins? (try disabling them)

Have you used a scanner driver inside Photoshop? (try removing the TWAIN plugin, scanner drivers are notorious for causing problems)

Have you printed anything before this problem occurs? (printer drivers can also cause some problems)

|

Mark as:

Currently Being Moderated

48. Dan_Perfect,

Mar 7, 2010 4:08 AM in reply to Chris Cox

Report

Hi again

Well its not just the OP that this happens to..

Although I dont seem to have his problem of the save location being important to success of the operation..

I have tried various combinations of RAM, tested it exhaustively, and it makes no difference to the proliferation of the memory error reports, and eventually to the crashing of CS4, most often in a save operation. I have reinstalled the system, run diskwarrior, disk utility etc etc, and removed all 3rd party plugins. Changed the memory settings in CS4, and changed scratch disk allocations. Don't know what else to do..

All I can do at the moment is save at 10min intervals & hope each time that I get lucky.

|

Mark as:

Currently Being Moderated

49. Chris Cox,

Mar 7, 2010 6:20 PM in reply to Dan_Perfect

Report

Dan - what OS version are you using? Part of what you describe sounds like MacOS 10.6 bugs (mostly fixed in 10.6.2).

|

Mark as:

Currently Being Moderated

50. davidsanger,

Mar 26, 2010 10:51 PM in reply to MuggeGHQ

Report

I also just had the same problem as the OP, repeated malloc errors during a save. The console logs also said

Mar 26 22:08:41 MacPro Adobe Photoshop CS4[20718]: *** process 20718 exceeded 500 log message per second limit - remaining messages this second discarded ***

Running Activity Monitor and inspecting the Photoshop process, the first frame referred to the save dialog routine and a semaphore wait.

Could the OS call be hanging and unable to complete the calls necessary to start saving the file?

There is no disk activity and file was never written at all.

MacPro OS10.6.2 10GB memory

|

Mark as:

Currently Being Moderated

51. Chris Cox,

Mar 27, 2010 2:30 PM in reply to davidsanger

Report

Well, that message just says that the log got a lot of messages - it doesn't say anything about what the error was.

semaphore_wait usually means that the app is waiting for the OS to complete something.

|

Mark as:

Currently Being Moderated

52. MuggeGHQ,

Jun 21, 2010 7:00 AM in reply to Chris Cox

Report

Hi.

Now i have another strange log error.

Photoshop CS4 Mac OS X 10.5.8

Beskrivelse: Logarkiv til systembegivenheder

Størrelse: 180 KB

Sidst ændret: 21/06/10 15.23

Placering: /var/log/system.log

Seneste indhold: ...

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextMoveToPoint: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextAddLineToPoint: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextDrawPath: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextRestoreGState: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextSaveGState: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextSetLineCap: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextSetLineJoin: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextSetLineWidth: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextBeginPath: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextMoveToPoint: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextAddLineToPoint: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextDrawPath: invalid context

Jun 21 15:21:35 mugge [0x0-0x78078].com.adobe.Photoshop[24045]: Mon Jun 21 15:21:35 mugge.local Adobe Photoshop CS4[24045] <Error>: CGContextRestoreGState: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextSaveGState: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextSetLineCap: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextSetLineJoin: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextSetLineWidth: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextBeginPath: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextMoveToPoint: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextAddLineToPoint: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextDrawPath: invalid context

Jun 21 15:21:35 mugge Adobe Photoshop CS4[24045]: CGContextRestoreGState: invalid context