matplotlib-devel Mailing List for matplotlib

In the trunk, I noticed that relim() followed by autoscale_view() do not have 
the same behavior as they did with the old transforms branch. For example:
l,=plot([1,2,3])
l.set_ydata([4,5,6])
gca().relim()
gca().autoscale_view()
draw()
used to produce the same output as
plot([4,5,6])
but now it is equivalent to 
plot([4,5,6])
ylim(1,6)
Darren

Michael Droettboom skrev:
> I haven't seen this issue. It may just be a dirty compilation problem. 
> Often distutils doesn't rebuild enough. Try removing the build 
> directory and then build/install.
> 
> If that's not the case, we'll need to track down which font is tripping 
> it up. Set "verbose.level" to "debug-annoying" and then send us the output.
> 
I get the crash on font orlando.ttf. If I delete this font there is no 
crash.
/Jörgen

Michael Droettboom wrote:
> Thanks for finding this.
> 
> This should be fixed in r4881. It was a simple reference counting bug.
> 
> Please let me know if you still see leaks.
That fixed it here. Thank you!
Eric

I haven't seen this issue. It may just be a dirty compilation problem. 
 Often distutils doesn't rebuild enough. Try removing the build 
directory and then build/install.
If that's not the case, we'll need to track down which font is tripping 
it up. Set "verbose.level" to "debug-annoying" and then send us the output.
Cheers,
Mike
Jörgen Stenarson wrote:
> Hi
> 
> today after upgrading to the latest svn (r4880 compiled with mingw) and 
> deleting fontManager.cache I got the following message and a crash
> 
> c:\python\>python
> Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)] on 
> win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pylab
> Assertion failed: ob_refcnt == 0, file CXX\cxx_extensions.cxx, line 1128
> 
> This application has requested the Runtime to terminate it in an unusual 
> way.
> Please contact the application's support team for more information.
> 
> restoring my old fontManager.cache I can successfully use matplotlib.
> 
> c:\python\>python
> Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)] on 
> win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pylab
> >>>
> 
> 
> I tried backdating matplotlib 40 revisions and got the same result. So 
> it is not a new problem.
> 
> Any one else seeing this?
> 
> /Jörgen
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Thanks for finding this.
This should be fixed in r4881. It was a simple reference counting bug.
Please let me know if you still see leaks.
Cheers,
Mike
Eric Firing wrote:
> Rob Hetland wrote:
>> I am using the new transforms version of MPL (the svn trunk), and 
>> found a memory leak in pcolor and pcolormesh. Be warned, I just 
>> reported a memory leak in the scikits delaunay package that Robert 
>> Kern was not able to reproduce, so it might be nice if someone could 
>> check this out. I am on Mac OS X, 10.4 using the latest svn versions 
>> of numpy and mpl. Here is the code that shows the leak:
>>
> 
> I have confirmed this on linux.
> 
> Eric
> 
>> from pylab import figure, close, ioff, savefig
>> from numpy.random import rand
>>
>>
>> ioff()
>>
>> for n in range(1000):
>> fig = figure()
>> ax = fig.add_subplot(111)
>> data = rand(1000, 1000)
>> ax.pcolormesh(data)
>> savefig('foo.png')
>> close(fig)
>> print n
>>
>>
>>
>> I get over a gig in real and virtual memory (over 2 gig total) by 
>> n=30. I tried both pcolor and pcolormesh, as well as deleting 
>> various objects, clearing the axis, etc.
>>
>> -Rob
>>
>> ----
>> Rob Hetland, Associate Professor
>> Dept. of Oceanography, Texas A&M University
>> http://pong.tamu.edu/~rob
>> phone: 979-458-0096, fax: 979-845-6331
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Hi
today after upgrading to the latest svn (r4880 compiled with mingw) and 
deleting fontManager.cache I got the following message and a crash
c:\python\>python
Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)] on 
win32
Type "help", "copyright", "credits" or "license" for more information.
 >>> import pylab
Assertion failed: ob_refcnt == 0, file CXX\cxx_extensions.cxx, line 1128
This application has requested the Runtime to terminate it in an unusual 
way.
Please contact the application's support team for more information.
restoring my old fontManager.cache I can successfully use matplotlib.
c:\python\>python
Python 2.4.3 (#69, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)] on 
win32
Type "help", "copyright", "credits" or "license" for more information.
 >>> import pylab
 >>>
I tried backdating matplotlib 40 revisions and got the same result. So 
it is not a new problem.
Any one else seeing this?
/Jörgen

Rob Hetland wrote:
> I am using the new transforms version of MPL (the svn trunk), and 
> found a memory leak in pcolor and pcolormesh. Be warned, I just 
> reported a memory leak in the scikits delaunay package that Robert 
> Kern was not able to reproduce, so it might be nice if someone could 
> check this out. I am on Mac OS X, 10.4 using the latest svn versions 
> of numpy and mpl. Here is the code that shows the leak:
> 
I have confirmed this on linux.
Eric
> 
> from pylab import figure, close, ioff, savefig
> from numpy.random import rand
> 
> 
> ioff()
> 
> for n in range(1000):
> fig = figure()
> ax = fig.add_subplot(111)
> data = rand(1000, 1000)
> ax.pcolormesh(data)
> savefig('foo.png')
> close(fig)
> print n
> 
> 
> 
> I get over a gig in real and virtual memory (over 2 gig total) by 
> n=30. I tried both pcolor and pcolormesh, as well as deleting 
> various objects, clearing the axis, etc.
> 
> -Rob
> 
> ----
> Rob Hetland, Associate Professor
> Dept. of Oceanography, Texas A&M University
> http://pong.tamu.edu/~rob
> phone: 979-458-0096, fax: 979-845-6331
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

I am using the new transforms version of MPL (the svn trunk), and 
found a memory leak in pcolor and pcolormesh. Be warned, I just 
reported a memory leak in the scikits delaunay package that Robert 
Kern was not able to reproduce, so it might be nice if someone could 
check this out. I am on Mac OS X, 10.4 using the latest svn versions 
of numpy and mpl. Here is the code that shows the leak:
from pylab import figure, close, ioff, savefig
from numpy.random import rand
ioff()
for n in range(1000):
 fig = figure()
 ax = fig.add_subplot(111)
 data = rand(1000, 1000)
 ax.pcolormesh(data)
 savefig('foo.png')
 close(fig)
 print n
I get over a gig in real and virtual memory (over 2 gig total) by 
n=30. I tried both pcolor and pcolormesh, as well as deleting 
various objects, clearing the axis, etc.
-Rob
----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331