Updates:
Status: Available
Owner: ---
Labels: HelpWanted
Comment #5 on issue 9245 by [email protected]: Fontconfig memory leaks on
Linux?
http://code.google.com/p/chromium/issues/detail?id=9245
FcFini didn't seem to help. It's really not clear to me which bits from
Fc*() we're
supposed to free or not. I also tried freeing the FcConfig*, but that was
bad
because it's set as the default config; again, unlcear to me whether it's
ever ok to
free it.
From that Pidgin bug, there's also:
"Since fontconfig does not use pointers to chain its elements together but
offsets of one location to the next (since it has to work with mmaped files
as
well), valgrind cannot determine the reachability of the fontconfig blocks
and
hence produces false positive reports."
Ugh. I'm giving up.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
