Take a look at the details in bug 32872. The issue is occurring again in 3.4 Beta 2.
*** This bug has been marked as a duplicate of bug 32872 ***