On Thu, Jul 31, 2008 at 10:37 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Yes, it looks like _ttconv.cpp is the culprit here. Sloppy reference
> handling (and I say that as the author of that file...) I've committed some
> changes to SVN that seem to remove the leaks with memleak_hawaii3.
Yes, it looks like _ttconv.cpp is the culprit here. Sloppy reference
handling (and I say that as the author of that file...) I've committed
some changes to SVN that seem to remove the leaks with
memleak_hawaii3.py and the PDF and PS backends.
Cheers,
Mike
Michael Droettboom wrote:
> I'm just
I'm just getting back from vacation and will add this to my TODO list.
I have some thoughts...
Cheers,
Mike
Eric Firing wrote:
> John Hunter wrote:
>
>> On Sat, Jul 26, 2008 at 7:20 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>>
>>
>>> The attached script gives a quick and simple illustr
John Hunter wrote:
> On Sat, Jul 26, 2008 at 7:20 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> The attached script gives a quick and simple illustration of the pdf backend
>> memory leak noted earlier by Paul Kienzle. It seems to be entirely related
>> to rendering text. Adding axes, lines, a
On Sat, Jul 26, 2008 at 7:20 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> The attached script gives a quick and simple illustration of the pdf backend
> memory leak noted earlier by Paul Kienzle. It seems to be entirely related
> to rendering text. Adding axes, lines, and images does not seem to
The attached script gives a quick and simple illustration of the pdf
backend memory leak noted earlier by Paul Kienzle. It seems to be
entirely related to rendering text. Adding axes, lines, and images does
not seem to matter, except insofar as adding an axes will trigger the
rendering of tex
