If the patch from I6ee241aca94a4db7bae2b359af7244dee6a53150 did not fix this problem, we're likely to still have that issue in 5.0 and 5.1 as well, please confirm.
If the patch from I6ee241aca94a4d b7bae2b359af724 4dee6a53150 did not fix this problem, we're likely to still have that issue in 5.0 and 5.1 as well, please confirm.