We could now reproduce and identify the problem. Will be fixed with werk #15489 in 2.1.0p28
Sorry for the delay