Comment 7 for bug 360158

I cannot reproduce this any longer with the fix applied in rev. #10463, so I guess this has been fixed!