From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Possible memory leak?
Date: Sun, 01 Feb 2009 16:47:38 +0100 [thread overview]
Message-ID: <4985C41A.5050303@elvenkind.com> (raw)
In-Reply-To: <68bfdc900902010644t71ec3644ue02d9fd29ef73282@mail.gmail.com>
Hi Yue Wang,
Yue Wang wrote:
> myfont = load_font('arial.ttf')
> myfont = load_font('arial.ttf')
> }
> and I can see the memory usage may ebb and flow, but actually it is
> leaking memory.
I also see a non-trivila leak (somewhere inside the fontforge library).
I will investigate further next week, it is not that massive. I get this
result for your input file, with 500 arial.ttfs (ArialMT version 3.0,
367112 bytes):
==8819== LEAK SUMMARY:
==8819== definitely lost: 16,965,191 bytes in 707,541 blocks.
==8819== possibly lost: 1,128 bytes in 22 blocks.
==8819== still reachable: 202,135,427 bytes in 81,127 blocks.
==8819== suppressed: 0 bytes in 0 blocks.
==8819== Rerun with --leak-check=full to see details of leaked memory.
So some 32kb per font. Noticeable, but not enormous. The growth in
'top' is probably caused more by memory fragmentation than by this leak.
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-02-01 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 14:44 Yue Wang
2009-02-01 15:03 ` Hans Hagen
2009-02-02 4:35 ` Yue Wang
2009-02-02 8:47 ` Hans Hagen
2009-02-02 9:13 ` Yue Wang
2009-02-02 22:14 ` Taco Hoekwater
2009-02-01 15:47 ` Taco Hoekwater [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4985C41A.5050303@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).