Anyway, the actual problem seems fixed in the latest mozc-2.17.2116.102 (error is not reproducible on my environment). See also PR/50281.