Re: FontConfig memory question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well, after reading your mail carefully again:

On Thu, Feb 13, 2014 at 7:39 AM, mathog <mathog@xxxxxxxxxxx> wrote:
> 45 bytes in 2 blocks are still reachable in loss record 26,064 of 38,661
>    at 0x402BE68: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
>    by 0x4FAFD42: ??? (in /usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
>    by 0x4FB0914: ??? (in /usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
>    by 0x4FADF4B: FcNameParse (in
> /usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)

[...]

This one may be okay because fontconfig do the memory allocation to
manage the non-built-in object types which isn't freed.

If you have any suspicious, that may be good to send me the whole log
or file a bug.

-- 
Akira TAGOH
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig




[Index of Archives]     [Fedora Fonts]     [Fedora Users]     [Fedora Cloud]     [Kernel]     [Fedora Packaging]     [Fedora Desktop]     [PAM]     [Gimp Graphics Editor]     [Yosemite News]

  Powered by Linux