Although I have not tested 6.7, this fault seems to have not been fixed on 6.6, but it seems that the commit I cited caused this fault. I can only say that I hope it can be fixed.
Rather, I just hope that this BUG is at least reported to them. 
Although I have not tested 6.7, this fault seems to have not been fixed on 6.6, but it seems that the commit I cited caused this fault. I can only say that I hope it can be fixed.
Rather, I just hope that this BUG is at least reported to them.