> OK, so I suggest we wait a bit for the problem to happen on 6.15. I have not reproduced this issue on 6.15.2 or 6.15.3.
I tested 6.12.34 tonight and the issue still exists. I have not found changes that can be cherry-picked to resolve the issue in 6.12.x. > Do you want to care for that then? I would appreciate some help with this so that I don't report incorrectly. Happy to continue providing information, but if someone could help with initiating the bug report, that would be helpful.
