There was no problem with other versions, but a similar problem occurred while testing version 5.5.1
@qufarhan, @Neo_Nex based on the tips of both of you