This problem was initially found on release 5.0.1, but seems to be still applicable on master.