I experienced the same issue earlier; it seems to have been introduced in one of the recent 2.52.x versions. However, the forum preview of version 3.0 doesn’t have the problem, so you may want to give that a shot. Per the announcement of the most recent version, it’s going to replace the 2.x line soon anyway:
