Re: [matplotlib-devel] MacOS X backend possible leak
Hi Hubert,
I just uploaded a fix for this bug to the matplotlib trunk svn repository (see
revision 8936). If you reinstall matplotlib from trunk, the bug should
disappear.
Best,
--Michiel.
--- On Thu, 1/27/11, Hubert Holin wrote:
> From: Hubert Holin
> Subject: [matplotlib-devel] MacOS X backend possible leak
> To: matplotlib-devel@lists.sourceforge.net
> Date: Thursday, January 27, 2011, 7:23 PM
> Paris (U.E.), le 28/01/2011
>
> Bonsoir
>
> I am trying to code a
> specialized data visualization technique (quite old and
> mostly forgotten), which I will release under the Python
> Software License. I want to customize the navigation bar
> read-out so as to give more relevant information than
> cartesian coordinates. I am not quite there yet, and may be
> missing a few things, but I have run into a problem.
>
> If I try to output a
> specific string to the navigation bar, using
>
>
> fig.canvas.toolbar.set_message("Toto")
>
> then sure enough the correct message appears in the right
> place. However, using the MacOS X backend, I get the leak
> message reproduced at the end of this message. I would much
> prefer to code in a backend-agnostic manner. Could someone
> please point me in the right direction?
>
> Merci
>
>
> Hubert Holin
>
> 8>< ===
> ><8
> 2011-01-27 15:22:27.892 Python[747:10b] ***
> _NSAutoreleaseNoPool(): Object 0x10ad544c0 of class
> NSCFString autoreleased with no pool in place - just
> leaking
> Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x103193750
> 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0
> 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840
> 0x1000e8300 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098
> 0x1000eaffc 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000ed950 0x1001188bc
> 0x100118d60 0x100133654 0x10f54 0x3)
> 2011-01-27 15:22:27.895 Python[747:10b] ***
> _NSAutoreleaseNoPool(): Object 0x10ad89aa0 of class
> NSSelectionArray autoreleased with no pool in place - just
> leaking
> Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff81618b2c
> 0x7fff81618abc 0x7fff815499b4 0x7fff815496b8 0x7fff81632598
> 0x7fff8152a814 0x7fff8152a2d8 0x103193770 0x1dd78
> 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0 0x1000ed840
> 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 0x1000e8300
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840
> 0x1000eb098 0x1000ed840 0x1000ed950 0x1001188bc 0x100118d60
> 0x100133654 0x10f54 0x3)
> 2011-01-27 15:22:27.897 Python[747:10b] ***
> _NSAutoreleaseNoPool(): Object 0x10ad70ad0 of class
> NSSelectionArray autoreleased with no pool in place - just
> leaking
> Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff8161a1e0
> 0x7fff81618e64 0x7fff81618abc 0x7fff815499b4 0x7fff815496b8
> 0x7fff81632598 0x7fff8152a814 0x7fff8152a2d8 0x103193770
> 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0
> 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840
> 0x1000e8300 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098
> 0x1000eaffc 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000ed950 0x1001188bc
> 0x100118d60 0x100133654 0x10f54 0x3)
> 2011-01-27 15:22:27.899 Python[747:10b] ***
> _NSAutoreleaseNoPool(): Object 0x1025f9350 of class
> NSSelectionArray autoreleased with no pool in place - just
> leaking
> Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff8161ad88
> 0x7fff816192f4 0x7fff81618abc 0x7fff815499b4 0x7fff815496b8
> 0x7fff81632598 0x7fff8152a814 0x7fff8152a2d8 0x103193770
> 0x1dd78 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0
> 0x1000ed840 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840
> 0x1000e8300 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098
> 0x1000eaffc 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000ed950 0x1001188bc
> 0x100118d60 0x100133654 0x10f54 0x3)
> 2011-01-27 15:22:27.901 Python[747:10b] ***
> _NSAutoreleaseNoPool(): Object 0x10ad6d480 of class
> NSAttributeDictionaryEnumerator autoreleased with no pool in
> place - just leaking
> Stack: (0x7fff82cc8d24 0x7fff82ba348c 0x7fff83041f08
> 0x7fff83042100 0x7fff83044bf0 0x7fff830449a8 0x7fff81619a58
> 0x7fff81618abc 0x7fff815499b4 0x7fff815496b8 0x7fff81632598
> 0x7fff8152a814 0x7fff8152a2d8 0x103193770 0x1dd78
> 0x1000e4910 0x100033df0 0x1dd78 0x1000eb2f0 0x1000ed840
> 0x1000eb098 0x1000eaffc 0x1000eaffc 0x1000ed840 0x1000e8300
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000eaffc
> 0x1000ed840 0x1000eb098 0x1000ed840 0x1000eb098 0x1000ed840
> 0x1000eb098 0x1000ed840 0x1000ed950 0x1001188bc 0x100118d60
> 0x100133654 0x10f54 0x3)
> 2011-01-27 15:22:27.903 Python[747:10b] ***
> _NSAutoreleaseNoPool(): Object 0x10ad8a8f0 of class
> NSCFDictionary autoreleased with no pool in place - just
> leaking
[matplotlib-devel] svn ancient history broken
I was trying to spot check the git repo by checking out the first commit that we have a history for in the log > git checkout 48111d043ec52f9afb511ac447438877b236e7f3 and notice that the main code directory 'matplotlib' was missing. I then tried to compare with a svn checkout of the same revision > svn co -r7 > https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/matplotlib > mpl7 and it had the same problem. I went forward several commits, and the log messages clearly indicate that many of the commits apply to matplotlib proper, but the code is missing. The first good svn version is apparently 541; the prior commit 540 had the log message "reorganizes py code". This was when we moved "matplotlib" to "lib/matplotlib" which I thought svn would handle gracefully. Any gurus have any idea if that early history is hidden somewhere in the bowels of svn? JDH -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 3:00 PM, John Hunter wrote: > I was trying to spot check the git repo by checking out the first > commit that we have a history for in the log > >> git checkout 48111d043ec52f9afb511ac447438877b236e7f3 > > and notice that the main code directory 'matplotlib' was missing. I > then tried to compare with a svn checkout of the same revision > >> svn co -r7 >> https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/matplotlib >> mpl7 > > and it had the same problem. I went forward several commits, and the > log messages clearly indicate that many of the commits apply to > matplotlib proper, but the code is missing. > > The first good svn version is apparently 541; the prior commit 540 had > the log message "reorganizes py code". > This was when we moved "matplotlib" to "lib/matplotlib" which I > thought svn would handle gracefully. Any gurus have any idea if that > early history is hidden somewhere in the bowels of svn? That was probably back when matplotlib was still using CVS, right? Does the CVS repository still exist? -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, 28 Jan 2011 14:00:40 -0600, John Hunter wrote: [clip] > The first good svn version is apparently 541; the prior commit 540 had > the log message "reorganizes py code". This was when we moved > "matplotlib" to "lib/matplotlib" which I thought svn would handle > gracefully. Any gurus have any idea if that early history is hidden > somewhere in the bowels of svn? svn ls -r7 -Rv https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/ There seems to be some code under "branches/jdhunter/matplotlib/". Is it the correct stuff? -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 2:57 PM, Pauli Virtanen wrote: > There seems to be some code under "branches/jdhunter/matplotlib/". > Is it the correct stuff? It's hard for me to know exactly if it the correct code (ie what was in the HEAD of the trunk at revision 7) but it is at least the right files in branches/jdhunter/matplotlib. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 2:09 PM, Darren Dale wrote: >> The first good svn version is apparently 541; the prior commit 540 had >> the log message "reorganizes py code". >> This was when we moved "matplotlib" to "lib/matplotlib" which I >> thought svn would handle gracefully. Any gurus have any idea if that >> early history is hidden somewhere in the bowels of svn? > > That was probably back when matplotlib was still using CVS, right? > Does the CVS repository still exist? I found a mailing list thread from Feb 2006 debating the switch from CVS to SVN, so yes, apparently I did the re-org while we were still on cvs which is why the history was lost. It may not be worth it, but I wonder if the matplotlib history from before the move to lib/ could be stitched back in. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 4:14 PM, John Hunter wrote: > On Fri, Jan 28, 2011 at 2:09 PM, Darren Dale wrote: > >>> The first good svn version is apparently 541; the prior commit 540 had >>> the log message "reorganizes py code". >>> This was when we moved "matplotlib" to "lib/matplotlib" which I >>> thought svn would handle gracefully. Any gurus have any idea if that >>> early history is hidden somewhere in the bowels of svn? >> >> That was probably back when matplotlib was still using CVS, right? >> Does the CVS repository still exist? > > I found a mailing list thread from Feb 2006 debating the switch from > CVS to SVN, so yes, apparently I did the re-org while we were still on > cvs which is why the history was lost. It may not be worth it, but I > wonder if the matplotlib history from before the move to lib/ could be > stitched back in. Stitched in from where? The jdhunter branch appears to only contain one commit, so it only contains the contents of matplotlib/ for rev4. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 4:41 PM, Darren Dale wrote: > Stitched in from where? The jdhunter branch appears to only contain > one commit, so it only contains the contents of matplotlib/ for rev4. It's not a completely fleshed out thought, but if we got the cvs repo before the directory move, did cvs to svn on that repo, and then converted that to git, we might be able to stitch the two git histories together, one from before the move and one after. JDH -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 6:56 PM, John Hunter wrote: > On Fri, Jan 28, 2011 at 4:41 PM, Darren Dale wrote: > >> Stitched in from where? The jdhunter branch appears to only contain >> one commit, so it only contains the contents of matplotlib/ for rev4. > > It's not a completely fleshed out thought, but if we got the cvs repo > before the directory move, did cvs to svn on that repo, and then > converted that to git, we might be able to stitch the two git > histories together, one from before the move and one after. That might be possible. Do you have access to the cvs repo? -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] svn ancient history broken
On Fri, Jan 28, 2011 at 5:58 PM, Darren Dale wrote: >> It's not a completely fleshed out thought, but if we got the cvs repo >> before the directory move, did cvs to svn on that repo, and then >> converted that to git, we might be able to stitch the two git >> histories together, one from before the move and one after. > > That might be possible. Do you have access to the cvs repo? Apparently not > cvs -z3 -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/matplotlib co -P > matplotlib cvs [checkout aborted]: connect to cvs.sourceforge.net(216.34.181.96):2401 failed: Connection refused Amazing how fragile digital data is! Well, there isn't much real use for history that old, except it's sometimes fun to see how small mpl used to be :-) While I was poking around in git though, it was certainly nice how fast you could switch the current directory to different revisions. JDH -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] git-svn matplotlib mirror
On 1/25/11 1:06 PM, Darren Dale wrote: > On Tue, Jan 25, 2011 at 1:31 PM, Pauli Virtanen wrote: >> Tue, 25 Jan 2011 12:19:37 -0500, Darren Dale wrote: >>> There is a potential problem converting the entire basemap history to >>> git. In svn commit 4418, trunk/toolkits had basemap and basemap-testing >>> directories. In commit 4419, basemap was renamed basemap-0.9.6.1, so >>> there was only basemap-0.9.6.1 and basemap-testing. In commit 4420, >>> basemap-testing is renamed basemap. The git history only goes back as >>> far as svn4420, it looks like the conversion routines get confused by >>> the temporary absence of the basemap directory. >>> >>> I'm trying to find a workaround, but if I can't... ? >> You can maybe do it like this: >> >> 1) Write matplotlib.rules so that all of the directories where basemap >> stuff has been ends in the basemap repository. (I'm assuming this does >> not error out...) > Aha! I thought I had tried that. Thanks. > >> 2) This will create a number of separate heads in the basemap repo that >> do not share common history. >> >> 3) Add graft rules in matplotlib.grafts to stitch the disconnected >> history graphs together. > Mercifully, the latest checkout of svn2git seems to take care of that. > I've developed a wicked headache. > > Jeff, the repository is temporarily available at > https://github.com/darrendale/basemap . It would be really helpful if > you would have a look at the network graph at > https://github.com/darrendale/basemap/network to make sure there are > no surprises, maybe clone the repository and check that the working > directory is identical to your svn checkout. > > Darren Darren: https://github.com/darrendale/basemap looks fine, thanks! -Jeff -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
