As given, the code signals either an address vector or a prefix vector from dhcpv6_client_node_fn to thread-0 report processes; then promptly vec_frees the address / prefix vectors. Needess to say, that's a horrible idea.

Patch on the way.

This took several days' worth of expert time to root-cause, in the context of an unrelated patch failing verification.