Hello @Louis,
Regarding the fix from 1.2.9.5.3:
Does this change have any impact on this bug or are they unrelated?