It seems that my experience with valgrind was affected by some specific code paths that might have had issues and confused valgrind (and thus me).[[BR]]
It seems that I came to a wrong conclusion that valgrind does not count calloc() and memset() as a valid initializers for allocated memory. As a result in multiple places I started to explicitly initialize the members of the structures.[[BR]]
In some cases it makes sense but usually does not. The patch submitted recently uses calloc() and does not have any issues with valgrind. So this bug calls for review of the places where different context and config structures are allocated and refactoring of the initialization code.