I suspect this is pointing at the wrong bug. We can't tell without a detailed stack trace. It's possible this should be pointing at bug 1712306 instead.
I suspect this is pointing at the wrong bug. We can't tell without a detailed stack trace. It's possible this should be pointing at bug 1712306 instead.