This is definitely a dupe of 1292971. That bug does not occur with version 3.1.16. I encourage people to upgrade if they encounter this issue. *** This bug has been marked as a duplicate of bug 1292971 ***