Although I can't reproduce it, I added if protection in revision#68514.

This bug is fixed. Thanks for your report.