Comment 46 for bug 91849

Thanks for getting that backtrace, that illuminates the situation better. However it doesn't appear to be something trivial like a null pointer dereference.

Next step for this bug is to go upstream for further analysis.