Make it a bit more explicit that we fill in a struct field, in an attempt to find a leak that valgrind knows it exists, but cannot make explicit how.
Make it a bit more explicit that we fill in a struct field, in an
attempt to find a leak that valgrind knows it exists, but cannot make
explicit how.

The leak is really related to the second thread (if I switch it around,
it's the first) which is the thread that does the cleanup.  Logging
shows the freeing and destroying is run, so what on earth happens
here... does the thread get lost somehow?

zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb