Create message crashes while running Google Filestream (Not Responding) with nsTArray_Impl<T>::RemoveElementsAtUnsafe and other random signatures
If Filestream is running, then selecting Reply or New message will cause Thunderbird to immediately crash and force close.
Could this be something to do with Windows handling a new message default app or something similar?
Windows 10 device, clean os install resolved the issue for about a week but same issue returned. I am able to close Filestream and then Thunderbird will allow the message to be created and sent. Need to be able to run filestream constantly though. Google cloud support was reported and there is no issue with Filestream. At least one other user on a different device in the office uses both programs without issue. The device has no third party antivirus, and TB was added to the firewall exceptions.
Upravil uživatel Wayne Mery dne
Všechny odpovědi (10)
Also there are no addons installed, and the result is appearing the same when TB is started in safemode.
Human, please post your crash IDs here in the topic. See https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports
Crash Reports for the Last 3 Days Report ID Submitted bp-974ab55b-dc80-4661-8abf-993f70200122 1 minute ago bp-965e9848-ee65-4abe-ad90-03ee20200121 1 hour ago bp-96f10076-eef7-4243-b669-615980200121 1 hour ago
Wayne Mery said
Human, please post your crash IDs here in the topic. See https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports
Was that what you needed Wayne?
Human said
Crash Reports for the Last 3 Days Report ID Submitted bp-974ab55b-dc80-4661-8abf-993f70200122 arena_t::DallocSmall | je_free | nsTArray_Impl<T>::RemoveElementsAtUnsafe | TimerThread::RemoveLeadingCanceledTimersInternal no bug report 1 minute ago bp-965e9848-ee65-4abe-ad90-03ee20200121 mozilla::CycleCollectedJSRuntime::JSObjectsTenured 1 hour ago https://bugzilla.mozilla.org/show_bug.cgi?id=1584796 bp-96f10076-eef7-4243-b669-615980200121 je_free | nsTArray_Impl<T>::RemoveElementsAtUnsafe | TimerThread::RemoveLeadingCanceledTimersInternal no bug report 1 hour ago
Thanks for the crash IDs. None of these crash signatures are common - in fact extremely rare. I'm not sure what can be done. Have to give it a think.
Wayne Mery said
Thanks for the crash IDs. None of these crash signatures are common - in fact extremely rare. I'm not sure what can be done. Have to give it a think.
Thank you for the response. I will replace the device in question. Hopefully the problem won't return but I will report back if an issue persists on the new device.
You're already on Windows 10. Is it an old device?
Wayne Mery said
You're already on Windows 10. Is it an old device?
No, I believe the o/s was native to the device. I think it's only 3 years old or so max but I could be wrong, IIRC it was a Dell p70f Inspiron 7573 2-in-1.
Were you able to make progress?
That device has been replaced and the issue has not returned on the new device with the same software setup.