Comment 2 for bug 1548402

We are currently looking into the issue but we have been unable to reproduce so far.