A bitmask is 64 bits, but integer immediates are passed as int in varargs, which happen to be 32 bit with high probability. This triggered a valgrind jump-relies-on-uninitalized-value report well away from the site, since it doesn't trigger on stack accesses, and there must have been enough zeroes to stop g_object_set at the right place.