I dont see this being fixed in the release notes.But i do remeber this is a very old issue and there was a case open for this long back and it was even escalated to backline engineers
So i would request you to call support and just confirm if there is a patch or workaround for this issue.