Project

General

Profile

Actions

Bug #11954

open

Pango (libfontconfig) memory leaks

Added by Matthias Van Ceulebroeck 11 months ago. Updated 5 days ago.

Status:
Review
Priority:
Normal
Assignee:
Target version:
Start date:
09/15/2023
Due date:
% Done:

0%

Estimated time:

Description

When using Pango with Address Sanitizer, a lot of leaks are reported, a lot of them coming from libfontconfig.
Some of them may be inherent to this library, but some of them could be caused by Wt's use.

A report for a small wt example that renders text to a PDF, using Pango

Wt::WPdfImage pdfImage("4cm", "3cm");
{
  Wt::WPainter p(&pdfImage);
  p.drawText(Wt::WRectF(0, 0, 20, 20), { Wt::AlignmentFlag::Left }, "Some text");
}
std::ofstream f("output.pdf", std::ios::out | std::ios::binary);
pdfImage.write(f);

results in a lot of leaks: SUMMARY: AddressSanitizer: 599399 byte(s) leaked in 14274 allocation(s).


Related issues 1 (1 open0 closed)

Related to Bug #12844: Further investigate remaining libfontconfig memory leakNew07/22/2024

Actions
Actions #1

Updated by Matthias Van Ceulebroeck 9 months ago

  • Target version changed from 4.10.2 to 4.10.3
Actions #2

Updated by Matthias Van Ceulebroeck 9 days ago

  • Status changed from New to InProgress
  • Assignee set to Matthias Van Ceulebroeck
  • Target version changed from 4.10.3 to 4.11.0
Actions #3

Updated by Matthias Van Ceulebroeck 9 days ago

  • Status changed from InProgress to Review
  • Assignee deleted (Matthias Van Ceulebroeck)
Actions #4

Updated by Marnik Roosen 5 days ago

  • Assignee set to Marnik Roosen
Actions #5

Updated by Matthias Van Ceulebroeck 5 days ago

  • Related to Bug #12844: Further investigate remaining libfontconfig memory leak added
Actions

Also available in: Atom PDF