Comment 9 for bug 388250

This is getting quite a few duplicates now. Could someone experiencing this bug please follow my instructions above to get a backtrace with the --sync option. Without it, we won't know for sure which call is generating the error, and any effort to fix it will therefore just be guess work and speculation. I've got no way to trigger the crash here.