Skip to content

ci: suppress known libass fontconfig LSAN leak#17869

Open
llyyr wants to merge 1 commit intompv-player:masterfrom
llyyr:suppress-libass-fontconfig-leak
Open

ci: suppress known libass fontconfig LSAN leak#17869
llyyr wants to merge 1 commit intompv-player:masterfrom
llyyr:suppress-libass-fontconfig-leak

Conversation

@llyyr
Copy link
Copy Markdown
Contributor

@llyyr llyyr commented May 3, 2026

Pending upstream fix libass/libass#924

@llyyr llyyr force-pushed the suppress-libass-fontconfig-leak branch 2 times, most recently from 2e15216 to ba5d22f Compare May 3, 2026 08:04
libfontconfig intentionally retains global state for the process
lifetime and this isn't fixable without risking UAF in other fontconfig
users.

See: libass/libass#924
@llyyr llyyr force-pushed the suppress-libass-fontconfig-leak branch from ba5d22f to 38e1b48 Compare May 3, 2026 08:29
Comment thread .lsan_suppressions
@@ -0,0 +1 @@
leak:libfontconfig.so
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with debug info we can be more specific here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking of introducing a lsan_disable/lsan_enable macro and wrapping the function call behind it instead. Do you think that's a good idea?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer external suppression myself.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we merge this for now to unbrick ci? We can refine this file later once we have debug symbol, and I could easily patch libass with libass/libass#925 if that gets upstreamed too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants