Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Constant Thunderbird crashes

  • 1 èsì
  • 0 ní àwọn ìṣòro yìí
  • Èsì tí ó kẹ́hìn lọ́wọ́ Mapenzi

more options

After months of constant Thunderbird crashes and hundreds of crash reports, and as many attempts at trying to resolve the issue but without any resolution, I am now getting the following message when Thunderbird crashes:

Thunderbird had a problem and crashed. Unfortunately the crash reporter is unable to submit a report for this crash.

Details: Expected value at line 1 column 1

I have version 128.5.2esr installed, but the issues started well before this version you can see the information in the crash reports if you want to look at them. I have tried Troubleshooting Mode, and can confirm the issue persists. I have also noticed that the one IMAP account I have attempts to redownload all messages from the mail server - it never completes because Thunderbird always crashes first. Aside from the obvious request for troubleshooting suggestions on the primary crash issue, I have three additional questions:

1. Is there a way for me to isolate that IMAP account, in another profile or such, to see if that account or server is contributing to the issue?

2. How is the crash report interpreted - i.e. where do I look to see the actual cause of the crash? In the "Details" tab the CRASH REASON and CRASH ADDRESS are not very informative to the average user.

3. What is the best way to provide a list of crash reports - I've had nearly 30 over the past few days, and - literally - hundreds since the issue began in October (which did not appear to coincide with anything in particular - e.g. new hardware or software, or TB update. Is is acceptable to post a list in the body of this thread, or as a txt document, or .... ?

BTW, running this on a Windows 10 22H2 machine, i9-14900KS, 32Gb DDR5, previously nVidia Quadro P5000 now Intel Arc A770 Graphics. Yes, have tried rebuilding POP3 folders, and yes I have a backup of my profile, which is about 35Gb in size.

TIA

After months of constant Thunderbird crashes and hundreds of crash reports, and as many attempts at trying to resolve the issue but without any resolution, I am now getting the following message when Thunderbird crashes: ''Thunderbird had a problem and crashed. Unfortunately the crash reporter is unable to submit a report for this crash. Details: Expected value at line 1 column 1'' I have version 128.5.2esr installed, but the issues started well before this version you can see the information in the crash reports if you want to look at them. I have tried Troubleshooting Mode, and can confirm the issue persists. I have also noticed that the one IMAP account I have attempts to redownload all messages from the mail server - it never completes because Thunderbird always crashes first. Aside from the obvious request for troubleshooting suggestions on the primary crash issue, I have three additional questions: 1. Is there a way for me to isolate that IMAP account, in another profile or such, to see if that account or server is contributing to the issue? 2. How is the crash report interpreted - i.e. where do I look to see the actual cause of the crash? In the "Details" tab the CRASH REASON and CRASH ADDRESS are not very informative to the average user. 3. What is the best way to provide a list of crash reports - I've had nearly 30 over the past few days, and - literally - hundreds since the issue began in October (which did not appear to coincide with anything in particular - e.g. new hardware or software, or TB update. Is is acceptable to post a list in the body of this thread, or as a txt document, or .... ? BTW, running this on a Windows 10 22H2 machine, i9-14900KS, 32Gb DDR5, previously nVidia Quadro P5000 now Intel Arc A770 Graphics. Yes, have tried rebuilding POP3 folders, and yes I have a backup of my profile, which is about 35Gb in size. TIA

All Replies (1)

more options

You can isolate the suspicious IMAP account by removing it temporarily without removing the message data. It would be very interesting to know the size of the INBOX folder in the suspîcious account.

Helpful?

Béèrè ìbéèrè

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.