Has this issue been resolved in the latest release? (4.52)