Re: [Valgrind-users] Many false positives "Mismatched free() / delete / delete []"

[David F. <fa...@kd...>]

I found it.

Using "step" in gdb showed that the new calls that valgrind complains about
go into.... qtwebengine/src/3rdparty/chromium/base/allocator/allocator_shim.cc

146├>void* ShimCppNew(size_t size) {
147│   const allocator::AllocatorDispatch* const chain_head = GetChainHead();
148│   void* ptr;
149│   do {
150│     ptr = chain_head->alloc_function(chain_head, size);
151│   } while (!ptr && CallNewHandler());
152│   return ptr;
153│ }

Indeed chromium's allocator_shim_override_cpp_symbols.h says
SHIM_ALWAYS_EXPORT void* operator new(size_t size)
    SHIM_ALIAS_SYMBOL(ShimCppNew);

This is why it didn't happen in smaller testcases, it only happens when 
including some qtwebengine headers.

=> No valgrind bug, sorry for the noise. I am now going to yell at the 
qtwebengine/chromium people for polluting applications with their custom 
operator new...

-- 
David Faure, fa...@kd..., http://www.davidfaure.fr
Working on KDE Frameworks 5