@Regan Hello again. Re:
Just a notification that as of 3.9.2-53 this issue is now resolved:
Hope that helps.