Judging by the newness of the problem, the crash address and the logs, this looks like it's probably bug 1924220. But we will need you to follow the instructions in comment #2 to confirm that.
Judging by the newness of the problem, the crash address and the logs, this looks like it's probably bug 1924220. But we will need you to follow the instructions in comment #2 to confirm that.