Bug #12844: Further investigate remaining libfontconfig memory leak - Wt - Redmine

Actions

Copy link

Bug #12844

open

Further investigate remaining libfontconfig memory leak

Added by Matthias Van Ceulebroeck about 2 months ago. Updated about 2 months ago.

Status:

New

Priority:

Normal

Assignee:

Target version:

future

Start date:

07/22/2024

Due date:

% Done:

Estimated time:

Description

In #11954 a significant memory leak was resolved, but a smaller instance of a leak remains.
This seems to happen internally in libpango. The trace using leak sanitizer looks like:

Trace Trace

    #0 0x7f973297f887 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
    #1 0x7f972f17ea21  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1fa21)
    #2 0x7f972f181590  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x22590)
    #3 0x7f972f18bb7c  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2cb7c)
    #4 0x7f972de31b66  (/lib/x86_64-linux-gnu/libexpat.so.1+0xdb66)
    #5 0x7f972de2fecd  (/lib/x86_64-linux-gnu/libexpat.so.1+0xbecd)
    #6 0x7f972de30dbb  (/lib/x86_64-linux-gnu/libexpat.so.1+0xcdbb)
    #7 0x7f972de284e7  (/lib/x86_64-linux-gnu/libexpat.so.1+0x44e7)
    #8 0x7f972de34f93 in XML_ParseBuffer (/lib/x86_64-linux-gnu/libexpat.so.1+0x10f93)
    #9 0x7f972f18d332  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2e332)
    #10 0x7f972f18dae8  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2eae8)
    #11 0x7f972f18dc9d  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2ec9d)
    #12 0x7f972f189acb  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2aacb)
    #13 0x7f972de31b66  (/lib/x86_64-linux-gnu/libexpat.so.1+0xdb66)
    #14 0x7f972de2fecd  (/lib/x86_64-linux-gnu/libexpat.so.1+0xbecd)
    #15 0x7f972de30dbb  (/lib/x86_64-linux-gnu/libexpat.so.1+0xcdbb)
    #16 0x7f972de284e7  (/lib/x86_64-linux-gnu/libexpat.so.1+0x44e7)
    #17 0x7f972de34f93 in XML_ParseBuffer (/lib/x86_64-linux-gnu/libexpat.so.1+0x10f93)
    #18 0x7f972f18d332  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2e332)
    #19 0x7f972f18dae8  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2eae8)
    #20 0x7f972f1752c0  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x162c0)
    #21 0x7f972f16e72e  (/lib/x86_64-linux-gnu/libfontconfig.so.1+0xf72e)
    #22 0x7f972f1755dc in FcInit (/lib/x86_64-linux-gnu/libfontconfig.so.1+0x165dc)
    #23 0x7f972f3b6e00  (/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0+0xae00)
    #24 0x7f972f22fab0  (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x84ab0)
    #25 0x7f9730343ac2 in start_thread nptl/pthread_create.c:442
    #26 0x7f97303d584f  (/lib/x86_64-linux-gnu/libc.so.6+0x12684f)

A new thread is used to initialise the libfontconfig code, where it appears a leak occurs. This can be because of the code in that library, or the way that the pango library calls this functionality. This is to be investigated further.

Related issues 1 (1 open — 0 closed)