On Tuesday, 5 September 2023 04:43:52 PDT Ahmad Samir wrote:
> I see the same issue locally, so I used `git bisect`, which showed it's
> because in `checkErrorOutput(const QString , const QByteArray
> )` in tst_selftests.cpp, the code should return early for
> "silent" test, because the latter
On 27/8/23 05:36, Thiago Macieira wrote:
See https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1698516419
[...]
Looking at this log:
==19313==ERROR: LeakSanitizer: detected memory leaks
agent:2023/08/26 21:36:18 build.go:405: 3:
agent:2023/08/26 21:36:18 build.go:405: 3: Direct
On Sonntag, 27. August 2023 17:42:58 CEST Thiago Macieira wrote:
> On Sunday, 27 August 2023 02:35:39 PDT Ulf Hermann via Development wrote:
> > I've seen this one before. I suspect certain versions of fontconfig have
> > an internal memory leak. For me, it fixed itself after an upgrade of
> >
On Sunday, 27 August 2023 02:35:39 PDT Ulf Hermann via Development wrote:
> I've seen this one before. I suspect certain versions of fontconfig have
> an internal memory leak. For me, it fixed itself after an upgrade of
> some packages. Can we install debug symbols for fontconfig on the
>
==19383==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 48 byte(s) in 2 object(s) allocated from:
#0 0x7f26aec7ae48 in __interceptor_malloc (/usr/lib64/libasan.so.
5+0x109e48)
#1 0x7f26a8bcbc50 (/usr/lib64/libfontconfig.so.1+0xbc50)
#2 0x3d4c4c415f434bff
See https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1698516419
Two separate sets of changes are running into this problem, which means
neither can be at fault. Tthis must be some other configuration that changed in
the CI. The file in qt5.git that seems to control this build hasn't
