5 Replies Latest reply: Aug 23, 2011 1:44 PM by bTesla
bTesla Level 1 Level 1

Does anyone have a set of cache / diskCache settings that tune up shake 4.1 to work with 6K images?  I'm currently crashing about every 20 seconds or so with the following errror:



shake(1511,0xa0338540) malloc: *** mmap(size=104861696) failed (error code=12)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

error: memory allocation failed



I have a new 12core 48G RAM OSX 10.6 machine.


I made an attempt to create a custom memory.h file  (see below):


diskCache.cacheMemory = 512;

diskCache.cacheMemoryLimit = 1024;

diskCache.cacheSize = 51200;

diskCache.cacheMaxFileSize = 16*8192*4320;  //8K 16bit Holds 8K 10bit image

diskCache.cacheLocation = "/scratch/shake";

cache.cacheMemory = 256;

cache.cacheMemoryLimit = 512;


Shake still crashes. W/O the memory.h file.


Any help would be appricated...



  • BenB Level 6 Level 6

    Where is 6k file coming from?

    Machine isn't powerful enough, your hard drive pipeline isn't handling the file well enough.

    You may need a fibre RAID system to make this work.

  • Patrick Sheffield Level 7 Level 7

    Shake doesn't care one bit about speed. I don't see how  a fibre RAID would help one iota with crashing.

  • bTesla Level 1 Level 1

    If there is one thing I'm sure of its that this is not a disk speed issue.  Files are serverd from or 40TB pool with dual 10GigE fiber runs to each box.   I can real time stream stereo 6K, so thats not it.   On top of that everyting is cached to 48G of ram and 500G of local SSD disk in the Mac Workstation.


    I'm starting to suspect there may be some memory allocation errors in a few nodes (camera smooth, paint) in shake.  That or I may have a bad stick of ram. 

  • Patrick Sheffield Level 7 Level 7

    I also seem to recall issues with more than 8 cores with smoothcam and/or optical flow...

  • bTesla Level 1 Level 1

    Ya, I've run into that issue as well on one of our other boxes... adding [sys.maxThread = 4;] to a customUI.h file seemed to fix that.


    Didn't seem to help here though.