I checked the call stack again, and in my case, the cause seems to be “WorldGridMaterial” in the dumping state of the attached error log, so whether the same procedure can solve the problem may depend on each individual situation. By the way, there seems to be a problem with WorldGridMaterial since 5.4.x, which may be indirectly related to this problem.