I just can't imagine why this problem is not yet solved...
As with most bugs, probably because it is not easily reproduceable in a controlled environment or because there are way more bugs that they can handle and hence must prioritize them and this one is not imprortant enough to get any attention (I hope you have reported your issue to Apple to increase the chances to get this fixed).
Last edited: