Skip to content

Conversation

@rodarima
Copy link
Member

Fixes #435

It already was the caller responsibility, but it was documented as not
being so, with a todo comment. Until other implementation is provided,
this was leaking memory. No need to keep the const.
Allows detecting memory leaks on exit automatically.
Leaks from libfontconfig.so are excluded for now, as it doesn't seem to
be our fault. The gcc mechanism to suppress leaks doesn't seem to be
working, so we fallback to awk.

In the presence of leaks, that specific test will fail by returning
non-zero, but this will not be what we want for those tests that are
currently failing with XPASS. We will only consider the ones that are
passing as those targeted for leak detection.
@rodarima rodarima force-pushed the detect-memory-leaks branch from f9733c2 to 580622b Compare August 24, 2025 22:21
Breaking the loop causes missing leaks that are otherwise visible when
closing the tab.
@rodarima rodarima merged commit 6abc25e into master Aug 30, 2025
11 checks passed
@rodarima rodarima deleted the detect-memory-leaks branch August 30, 2025 14:24
@rodarima rodarima added this to the Release 3.3.0 milestone Aug 31, 2025
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.

Add leak checks to CI

2 participants