Please post your crash ID(s)

bp-3f94b9f2-0300-4c86-9107-d32990210428 latest bp-5d4ac52d-e1dd-4aa1-a1f3-77af20210429 bp-5e854c65-e1a1-4ecf-b284-5b2380210429 bp-6d825649-da5a-44f1-a948-bb1ef0210428 bp-6fa25086-f312-4562-866e-f64ba0210428 bp-9d99330d-a9a8-4d43-9ac0-e027b0210428 bp-9ecbdf20-8f85-4cda-aaea-db4b40210428 bp-9f965e90-c3bd-45e1-ae55-6aaac0210428 bp-15df85a2-a3f7-4d6a-bd3c-53bd70210428 first

Tried downgrading back to 78.8.0, 78.8.1, 78.9.0 and 78.9.1. Same crash. Crash happens some time after window opens and I can see my open tabs being built. Some of those crash IDs are safe mode IDs.

Thanks for any help you can offer. Am in crisis mode for work. Really need TB back.

Sorry, just realised the %appdata wasn't sorted by time. Here's full list. bp-5e854c65-e1a1-4ecf-b284-5b2380210429 bp-82adcadc-e6a7-48cf-8e0b-f8f970210429 bp-ec6dcc8f-f8c8-4b42-9016-3d7220210429 bp-c2f26df5-4eb4-4d26-934f-e1de30210429 bp-31c87062-a370-4fc7-a072-c9cad0210429 bp-c8ac9a92-7bb0-4538-b291-378d80210429 bp-f53da2ca-5fcb-40bf-b3cf-da69b0210429 bp-5d4ac52d-e1dd-4aa1-a1f3-77af20210429 bp-9f965e90-c3bd-45e1-ae55-6aaac0210428 bp-1621655b-a227-480c-ae33-19c0a0210428 bp-a5ff5619-07c9-4631-8084-cf6480210428 bp-e16b3a19-58e5-4318-8a37-eaa940210428 bp-74e6c946-da59-4b96-a8d7-a7d500210428 bp-2166bab9-774b-43ea-a3f4-54c060210428 bp-6fa25086-f312-4562-866e-f64ba0210428 bp-9d99330d-a9a8-4d43-9ac0-e027b0210428 bp-74e47057-a410-4c39-943e-287810210428 bp-9ecbdf20-8f85-4cda-aaea-db4b40210428 bp-15df85a2-a3f7-4d6a-bd3c-53bd70210428 bp-9441f206-6f78-4cfc-8898-20edb0210428 bp-38704164-7a33-4cad-84e5-355820210428 bp-c6d53024-dc15-473f-9ebe-b8d960210428 bp-6d825649-da5a-44f1-a948-bb1ef0210428 bp-945eabe6-4808-4003-9e65-2b5890210428 bp-666f0130-d6c1-450f-ae87-06cef0210428 bp-3f94b9f2-0300-4c86-9107-d32990210428 bp-f8b91680-5c37-4359-a6bf-6088d0210428

I see bp-38704164-7a33-4cad-84e5-355820210428 was in Thunderbird safe mode. Crash signature is @ mozilla::dom::Navigator::CheckProtocolHandlerAllowed

Try starting Windows in safe mode. Also, do you have any crashes prior to 4/21 ?

The quick solution would be to remove Avast and instead use Windows Defender.

https://support.mozilla.org/en-US/questions/1312718

https://support.mozilla.org/en-US/questions/1312586

The quick solution would be to remove Avast and instead use Windows Defender.

That could be a solid recommendation - but perhaps just disabling Mail Shield would solve the issue - it would be useful to know ... Because I'm not aware that we have other avast users currently reporting problems, plus my spot checks of crashes with this signature the vast majority do not have Avast.

Hi

Tried disabling mail shields first before posting here. No change. Have uninstalled Avast and enabled Defender which I thought would work as there was also a pending Avast update pre 1st crash. Still crashing. Latest Crash IDs both on standard run and TB safe mode as below. @Wayne - no, no crashes ever (or at least since TB3 in 2018). Only since 28/4 when updated to 78.10.0.

bp-3cf7230e-7f77-4f52-b734-98eef0210430 bp-30d21ba3-b70a-4c9f-9e83-dd7120210430 bp-64f294a3-c4ec-4729-83bf-073820210430 bp-071d7dd2-22b6-4ef2-9893-887410210430 bp-356c0f01-e37c-4c65-b7b4-2232a0210430 bp-e278c88d-be93-4135-a393-8aee70210430 bp-1bf52629-d53c-40d9-8f79-abe570210429

Again, thanks for any help you can offer.

Also to note TB doesn't crash in Windows safe mode.

Hi Tried disabling mail shields first before posting here. No change. Have uninstalled Avast and enabled Defender which I thought would work as there was also a pending Avast update pre 1st crash. Still crashing. Latest Crash IDs both on standard run and TB safe mode as below. @Wayne - no, no crashes ever (or at least since TB3 in 2018). Only since 28/4 when updated to 78.10.0. bp-3cf7230e-7f77-4f52-b734-98eef0210430 bp-30d21ba3-b70a-4c9f-9e83-dd7120210430 bp-64f294a3-c4ec-4729-83bf-073820210430 bp-071d7dd2-22b6-4ef2-9893-887410210430 bp-356c0f01-e37c-4c65-b7b4-2232a0210430 bp-e278c88d-be93-4135-a393-8aee70210430 bp-1bf52629-d53c-40d9-8f79-abe570210429 Again, thanks for any help you can offer.

These are also all @ mozilla::dom::Navigator::CheckProtocolHandlerAllowed

Someone pointed out to me that most of our crash reports have the OWL add-on installed.

Also to note TB doesn't crash in Windows safe mode.

Also to note TB doesn't crash in Windows safe mode.

This would suggest some non-Thunderbird code is involved. You wrote that you still crashed with Avast removed. So perhaps it is something else, or something in combination with the OWL add-on.

However it still crashes in TB Safe mode. Shouldn't safe mode be disabling all addons including OWL ? Also, I have created another instance of TB 78.10.0 in a different installation folder which is using OWL fine.

However it still crashes in TB Safe mode. Shouldn't safe mode be disabling all addons including OWL ?

Yes, that's a good point. So it must be something loading during Windows startup.

As I said though I've created a 2nd installation of 78.10 with a new profile, added my Outlook account, installed OWL and it works fine so think there's a problem in my original profile. Could really do with recovering my original profile as it has my address books, rules etc and much of my business workflow that would be a right pain to recreate.

What is on the Startup tab in Task Manager, that is being bypassed in Windows safe mode? If it's not AV causing the crash, what are other possibilities? Backup apps that run at startup can be an issue.

If you end up creating a new profile from Help/Troubleshooting, about:profiles, it's not too difficult to transfer data from the old profile,

https://support.mozilla.org/en-US/questions/1334460#answer-1409638

and might be faster than debugging the current profile. Besides local mail and address books, filters are easily copied by finding the msgFilterRules.dat files in the account subfolders of Mail or ImapMail.

Interestingly I found my old v68.12.1 (32-bit) in Program Files x86 which runs my profile fine. Strangely it also runs Office 365 Exchange with 2FA authentication which had ceased to work before. Also runs all my beloved old addons which had also ceased to work since latter upgrades. So, my profile is not corrupt and does therefore point to something buggy in 78.10.0.

Unfortunately that only worked momentarily. On restart TB complained about the fact the profile had been edited by a later version. So, in desperation, I've created a new profile so I can do some work. I copied as many files from v78.8 as I could work out but now my main issue is my addressbooks aren't showing up. I have 12 abook*.sqlite but they aren't showing up in address book. Are they referenced in a ini or something ?

You can open the profile that was declared 'edited by a later version' by launching Profile Manager with the downgrade switch, i.e. open a Run window (Winkey+R) and type

thunderbird.exe -p --allow-downgrade

then select the relevant profile.

But if you just have the abook-*.sqlite files that aren't showing up, they can be 'imported' with an awkward method: close TB, open the profile folder, rename abook.sqlite to abook.sqlite.old, rename abook-1.sqlite to abook.sqlite, open TB, create a new address book, drag the current contents of Personal Address Book to the new address book. Then close TB, delete abook.sqlite, rename abook-2.sqlite to abook.sqlite, open TB, create another new address book, drag the current contents of Personal Address Book to the new address book.

At the end of this process, close TB, delete abook.sqlite and rename abook.sqlite.old to abook.sqlite.

Hmm. Interesting. Running the command line on my v68 installation (x86) allows me access my old profile. However on next launch tried to access through my original v78.8 installation which worked initially but on next run went back to the crash error bp-81241d05-015c-4088-97e8-0e1d80210504

We're looking into this.

This appears to be caused by some HTML calling `registerProtocolHandler()` with a URL scheme that Thunderbird itself registers as internal handler, like "news" or "imap", and the Gecko function then crashes.

What would help us to know is exactly where the HTML renders which triggers this, and the HTML itself. Is it during Login, while reading a mail, a calendar invitation, or a opening a calendar event? Once we know where it's triggered from, we can see whether we can prevent it.