Thunderbird crashes with various crash signatures, caused by Bitdefender. mozilla::PromiseJobRunnable::Run // encoding_rs::mem::is_basic_latin_implr // JS::HeapObjectPostWriteBarrier // RtlpWaitOnCriticalSection ... Mutex::Lock
The latest Thunderbird releases have been crashing regularly, with these submitted reports. I'm trying to ascertain what I need to do to mitigate or eliminate the crashes.
bp-fff7f0cc-3bcf-4863-a97a-2da0b0241109 (submitted 5 minutes ago) bp-211988fe-edbc-4bd6-9f0b-22b8a0241109 (submitted 21 minutes ago) bp-e1d549ea-2933-4ed2-8bac-6c2ed0241108 (submitted 1 day ago) bp-0ec18bc9-e38b-4252-85e7-0cb5e0241108 (submitted 1 day ago) bp-44316ba1-928c-49e8-b7f0-3ac140241105 04-Nov-24, 7:22 PM bp-62666d35-b069-44c2-ab2c-3b6950241105 04-Nov-24, 7:22 PM bp-0631d697-4a78-482a-b0df-db8810241105 04-Nov-24, 7:22 PM bp-6d6b5962-f140-4532-b272-1f9bf0241105 04-Nov-24, 7:22 PM
etc, ad nauseum going back to 03 October.
由Wayne Mery于修改
所有回复 (3)
Almost every one of those crashes has a different crash signature, with uptime of 15 minutes to a day (on average), and none have bug reports.
Some show no add-ons running, so you have tried Thunderbird in Troubleshoot Mode? But some do: duplicateContactsManager@ddvo.net duplicateContactsManager 2.1.1 mailmerge@example.net Mail Merge 10.5.0 {2ab1b709-ba03-4361-abf9-c50b964ff75d} Signature Switch 2.18.1 {8845E3B3-E8FB-40E2-95E9-EC40294818C4} Quicktext
My money is on Bitdefender, or whatever is installed for 3DCONNEXION S.A.M. Try Windows start Windows in safe mode with networking enabled - https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode
Thanks,
Huzzah! This is interesting because BitDefender isn't installed on this PC, but crash reports shows two .dll files related to BitDefender: gemmauf64.dll and bdhkm64.dll
I'll do a seek and find on where those .dlls are located. Maybe I'll find something under that rock. ;-)
Still no luck. I've had 14 crashes in the last 2 days. I've disabled the Active Protect on Vipre (I learned that they use Bitdefender's module for this), and am working with 3DConnexion to see if they can offer assistance. In the meanwhile, can someone please explain where to look in the crash reports for the most viable suspect for the specific crash? The popup crash details often don't exactly correspond with the crash report itself. I need help navigating these crash report tabs to try and pinpoint the issue: Details; Crash annotations; Bugzilla; Modules; Raw Data and minidumps; Extensions; Telemetry Environment; Correlations; or Debug.
thanks again