Hi Vedran,
Just to keep you posted. This is the latest info I got from the engineering team:
"The solution for this defect has been identified and will be included in the next maintenance release estimated to be released in Oct 2016"
Kind Regards,
Brian