@sdeziel It looks like I can't trigger the bug anymore with 5.21.1-d46c406 so whatever my problem was probably got fixed in one of the last updates
@sdeziel It looks like I can't trigger the bug anymore with 5.21.1-d46c406 so whatever my problem was probably got fixed in one of the last updates