As we are the only two that has reported and confirmed this bug, and we both confirm that the 2.4.24 release has resolved/massive improvment on this bug I'd suggest closing it to remove developer effort.
As we are the only two that has reported and confirmed this bug, and we both confirm that the 2.4.24 release has resolved/massive improvment on this bug I'd suggest closing it to remove developer effort.