The error is *printed* because when you're tangled that far down inside deletion traces and namespace deletion callbacks, there's simply no route to report it sanely except via the background error message mechanism (and that's got a simple message printer attached).

Anyway, the questions are:

1. Why does this let this message through with valgrind in use?
2. Why does this *not happen* in other configurations?