Comment 1 for bug 1262638

There are two things failing in here. Valgrind is detecting both:

1) An uninitialised value jump.
2) A variety of "possible" leaks inside Google Test

Each of these things seems to be out of my control. I think this is one of the few projects under CI that's running its tests under Valgrind. Anyway, the easy fix is to add some suppressions for the Google Test ones. They're probably false positives. However I think it's unlikely that these failures are caused by the new Qt version. More likely by something else, (new google test?).