Re: [Matplotlib-users] Fwd: malloc error on show() oder x/ylabel()

[Hannes K. <ku...@pi...>]

Because of import- and compatibility issues I build everything from scetch some days ago. Now i only have one Python (2.7.1) installation and only one matplotlib version (1.0.1). In the /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ directory there's, too, only the matplotlib dir and the matplotlib-1.0.1-py2.7.egg-info … 

It was build from source; what has to be removed to uninstall matplotlib completely? Maybe it would help to rebuild it.

Best,
Hannes

Am 12.01.2011 um 17:55 schrieb Benjamin Root:

> 
> 
> On Wed, Jan 12, 2011 at 10:23 AM, Hannes Kutza <ku...@pi...> wrote:
> i think now it's mainly the savefig() that provokes that malloc error…
> 
> Anfang der weitergeleiteten E-Mail:
> 
>> Von: Hannes Kutza <ku...@pi...>
>> Datum: 12. Januar 2011 14:35:24 MEZ
>> An: mat...@li...
>> Betreff: malloc error on show() oder x/ylabel()
>> 
>> i'm running python 2.7, matplotlib-1.0.1, gcc 4.2.1 and grortran 4.2.1… when invoking (successful importing import matplotlib.pyplot as plt) plt.show() in combination with plt.xlabel or savefig("fig.ps") give me that nasty malloc error:
>> 
>> Python(19725,0x7fff7055fca0) malloc: *** error for object 0x102d8c6c0: pointer being freed was not allocated
>> *** set a breakpoint in malloc_error_break to debug
>> Abort trap
>> 
>> calling plt.show or x/ylabel("string..") alone doesn't get me that error…
>> 
>> cheers,
>> hannesk
> 
> 
> Hannesk,
> 
> Most likely the issue here is a bad or mixed build.  Assuming that you built the current install of matplotlib 1.0.1 from source, how did you have your previous install (packaged or from source)?  Did you completely remove that install before building the current install?
> 
> Ben Root
>