This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients mmokrejs, pitrou, skrah, tim.peters, vstinner
Date 2013-08-30.18:44:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377888246.48.0.902331487535.issue18884@psf.upfronthosting.co.za>
In-reply-to
Content
Now you have something to show the matplotlib folks - although they're not likely to get excited about leaking 40 bytes.

There is nothing Python can do about this.  matplotlib is responsible for free'ing the memory matplotlib allocates, just as Python is responsible for free'ing the memory Python allocates.  If _you_ wrote a C extension module, and did

char *p = (char *)malloc(40);

and never did a free(p) later, it would be the same kind of thing.
History
Date User Action Args
2013-08-30 18:44:06tim.peterssetrecipients: + tim.peters, mmokrejs, pitrou, vstinner, skrah
2013-08-30 18:44:06tim.peterssetmessageid: <1377888246.48.0.902331487535.issue18884@psf.upfronthosting.co.za>
2013-08-30 18:44:06tim.peterslinkissue18884 messages
2013-08-30 18:44:06tim.peterscreate