This was fixed in 6.3 release candidate 2. Final 6.3 has already been released, please update to 6.3.