Skip navigation
Currently Being Moderated

Strange system log error from Photoshop CS4

Apr 7, 2009 7:18 AM

Hi.

 

I keep getting this strange system log error from Photoshop CS4.

It comes after a wile when using PS CS4.

I tried to chance the memory settings and scratch disc to see if that helped. It didn't.

I also checked all my ram for anything bad. 16GB in my Mac Pro Intel OS X 10.5.6

Everything is updated to latest included Adobe apps.

 

This is the system log error

 

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** set a breakpoint in malloc_error_break to debug

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: Adobe Photoshop CS4(305,0x6a73720) malloc: *** mmap(size=132911104) failed (error code=12)

Apr  7 16:04:03 mugge [0x0-0x28028].com.adobe.Photoshop[305]: *** error: can't allocate region

 

And it keeps on until i close Photoshop.

 

Please anybody ?? i cant figure out what this means.

 

Thx for help.

Erik S

 
Replies 1 2 Previous Next
  • Pierre Courtejoie
    7,043 posts
    Jan 11, 2006
    Currently Being Moderated
    Apr 7, 2009 7:56 AM   in reply to MuggeGHQ

    "malloc" does sound like a contracted form of Memory Allocation.

    What are your current memory settings? Cache levels?

    How did you test the RAM? is it Apple RAM?

    did you use any of the extensions, like disable scratch compression, or Bigger Tiles?

     

    Take a look at these documents:

    Optimize performance in Photoshop CS4 on Mac OS

    Troubleshoot system errors or freezes in Photoshop CS4 (Mac OS)

     
    |
    Mark as:
  • Ramón G Castañeda
    11,247 posts
    Jul 27, 2006
    Currently Being Moderated
    Apr 8, 2009 2:10 AM   in reply to MuggeGHQ

    Have you monitored the temperature inside the machine?  An intermittently failing fan could be causing heat problems.  Just a hunch.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 8, 2009 9:32 AM   in reply to MuggeGHQ

    Hmm, I'm not sure what in Photoshop would keep allocating 128 Meg buffers.

     

    Sometimes that error shows when you're low on RAM, and Photoshop fails to allocate something - but then we try again with smaller buffers.

     

    My first guess is that the OS is trying to allocate something when called by Photoshop, and doesn't have a graceful recovery strategy.

    Next guess is a plugin misbehaving (third party, scripting or ACR).

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 8, 2009 9:33 AM   in reply to Pierre Courtejoie

    Doesn't look like a hardware problem, just software.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 8, 2009 10:41 AM   in reply to MuggeGHQ

    I also can't figure out what would be using an mmap (Photoshop itself doesn't use them).

     

    If you removed or disabled all the third party plugins, that should rule them out as the cause - but do double check the "about plugins" list to make sure they were disabled.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 16, 2009 5:08 AM   in reply to MuggeGHQ

    try photoshop in a new user.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 16, 2009 4:30 PM   in reply to MuggeGHQ

    At this point I would do an Archive and install of the OS and see if that fixes it.

     
    |
    Mark as:
  • Ramón G Castañeda
    11,247 posts
    Jul 27, 2006
    Currently Being Moderated
    Apr 17, 2009 11:52 AM   in reply to MuggeGHQ

    MuggeGHQ wrote:

     

    But i even tried a full clone of a 100% working HD from one of my other Mac Pro.

    Same thing ???  Its like this specific Mac Pro dosent like when there is 16GB of memory installed.

     

    Perhaps a bad or mismatched RAM module or two?  I'd start testing it with only two sticks at a time to ferret out the possibly problem one(s).

     
    |
    Mark as:
  • Ramón G Castañeda
    11,247 posts
    Jul 27, 2006
    Currently Being Moderated
    Apr 17, 2009 6:00 PM   in reply to MuggeGHQ

    MuggeGHQ wrote:

     

    Hi Ramón

     

    All memory blocks have been tested by me and the shop where i bought them.

     

    Mugge,

     

    The ultimate RAM test is Photoshop itself.

     

    All software RAM testers, like memtest, rember, etc., miss some problem RAM occasionally.

     

    Photoshop addresses even parts of the RAM module that software tests miss.  Even the tests used by engineers are not always definitive.

     

    The only way to make sure is to take all RAM sticks out, then put two back at a time and run Photoshop.  If you have actually done that, then fine, I must have missed that in your earlier posts.  But if you haven't done exactly what I've described, you simply cannot rule out bad or mismatched RAM.  It's that simple.

     

    I'll go back and re-read the entire thread now.

     
    |
    Mark as:
  • Ramón G Castañeda
    11,247 posts
    Jul 27, 2006
    Currently Being Moderated
    Apr 17, 2009 6:04 PM   in reply to MuggeGHQ

    This is what I found:

     

    MuggeGHQ wrote:

     

    I used the memtest for the memory testing and i had it running all night in 6 loops. Nothing.

     

     

    Pfffft!  

     
    |
    Mark as:
  • Ramón G Castañeda
    11,247 posts
    Jul 27, 2006
    Currently Being Moderated
    Apr 17, 2009 9:43 PM   in reply to MuggeGHQ

    That's very wise, Mugge.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2009 1:11 PM   in reply to MuggeGHQ

    That sounds like  you're running a plugin that uses the Qt framework for their user interface.  (Photoshop does not use Qt, or natively generate any warnings like that)

     

    You need to identify which plugin you are running when the error occurs, and report the problem to the plugin authors.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 28, 2009 2:33 PM   in reply to MuggeGHQ

    The mmap error is either a third party plugin, or some system driver.

     

    Photoshop does not use mmap.

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 29, 2009 3:50 PM   in reply to MuggeGHQ

    A system driver is part of the system: the operating system.

     

    Yes, you've posted the mmap error several times now, you can stop posting that now.

     

    I don't know about the Bridge error, but you might want to ask in the Bridge forum.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 30, 2009 12:27 PM   in reply to MuggeGHQ

    I doubt it.

     

    But a poorly written plugin might run into trouble when memory got tight.

     

    Again, the mmap errors are probably coming from a third party plugin, or some part of the OS.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2009 5:45 PM   in reply to MuggeGHQ

    As a FYI. I have this same problem with two brand new Mac Pro's (10.5.7) Both Running new CS4 installs. Both came with 3 GB of RAM problem started immediatly, I replaced all ram on both systems, bumping them up to 8GB each. Problem persists. These are pretty much vanilla setups. I am sure it is a software setting or driver issue, I just thought I would let you know it is not isolated.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2009 9:11 PM   in reply to mark-e-r

    I would say try a setting of 80% maximum.

     

    And perhaps this is hardware related and that the RAM that is defective could be that on your video card.

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points