@chris can you reliably reproduce on all 10.12.3 machines? (thus isolating the problem to something introduced in that update)