Hi @alojzy231
As you know from our investigation and different approaches checked, we don’t have a workaround for this problem so it has to be fixed at the core.
This issue is added in our internal backlog and awaits estimation and fixing. I will update you as soon as I have more accurate information.