1 Reply Latest reply: May 22, 2009 3:34 AM by Mephi
Mephi Level 1 Level 1 (0 points)
I'm using python (macpython 2.5) & matplotlib for huge data analyses and visualisation (with imagemagick and mplayer, I should add). While matplotlib (0.98.5.2) usually took enormous amounts of memory, (during a period of time up to 1.5 Gigs working memory) which isn't good, after updating to 10.5.7 (from 10.5.6), things got worse. After a couple of minutes in which a couple of hundred pngs, (800x600, just a scientific graph) were plotted, it would go RuntimeError on me. And not just that. Python would quit with an error code 12. Something to do with memory allocation, even if it's the first thing after booting up. Malloc and stuff.

I'm pretty sure it's a matplotlib-thing as, other datahandling code without matplotlib kept working.

Good news though: with the Enthought edition these troubles disappear. Completely.

MacBook (dec 2009), Mac OS X (10.5.7)
  • Mephi Level 1 Level 1 (0 points)
    Nevermind that, I still get this error:

    Python(9737) malloc: * mmap(size=65536) failed (error code=12)
    * error: can't allocate region
    * set a breakpoint in mallocerrorbreak to debug
    Python(9737) malloc: * mmap(size=65536) failed (error code=12)
    * error: can't allocate region
    * set a breakpoint in mallocerrorbreak to debug
    Python(9737) malloc: * mmap(size=65536) failed (error code=12)
    * error: can't allocate region
    * set a breakpoint in mallocerrorbreak to debug
    libpng error: zlib failed to initialize compressor

    which is an odd error since it has made 424 pngfiles without error. and memory wasn't full according to iStat.
    And python doesn't just quit after this error. It keeps running, filling up working space memory. Grr.