The problem disappeared in version 5.0.5 and 5.0.6 so I suppose the bug is fixed and this issue can be closed