This thread was archived. Please ask a new question if you need help.
Frequent Crashes opening a large email 15-20 mb and viewing in rapid succession various emails. No AV software. Partly related to notifications?
We've been using thunderbird for more than 20 years now at work. It has proven itself reliable and production ready. I am sorry to say in the last 5 years or so every update has been worse than the previous one becoming the least reliable piece of software ever. Constant crashing ie 8-10 times a day, lack of smtp communication with the servers, and other constant issues basically make this unusable.
PLEASE forget about aesthetics and concentrate on reliability.
Modified by Wayne Mery
All Replies (17)
Post a crash ID from Help/More Troubleshooting, Crash Reports. An ID is a string starting with bp-...
In the meantime, try running TB in safe/troubleshoot mode (hold Shift when launching TB), or run Windows in safe mode.
Done everything, safe mode, troubleshoot mode, disabled all add ons, prayed to IT god, yet to no avail.. It crashes all all pcs in the office for any reason.
bp-ea0f2d29-da3c-4135-8814-4a53f0211026 bp-8118c4e9-1097-40c8-97a2-e520c0211026 bp-03b94c8d-7c4b-40d3-97b9-bfa150211026 bp-cfb46d1a-5346-46a4-9fe9-c5aa80211026 bp-2b2ea9ac-b255-44cc-8b31-482860211026 bp-5ae8be52-9fef-48b6-a93e-6658b0211025 bp-d34ba288-6b8a-438f-ae0f-23ac50211025
I looked at all reports, and although there are different signatures and some have Bugzilla references, I couldn't find a common factor that would cause crashes. Try running Windows in safe mode on one system to test the effect of startup apps, drivers etc.
Which proves my point that there are common stability issues in the new releases of thunderbird. Surely 10 pcs running this using different OSs and environments all crashing without warning is a sign of deeper inherent issues in the latest releases. To my mind, any new releases should concentrate on that rather than new features. A business needs to use reliable stable software which can run without interruption, rather than see the email application crash in the midst of writing a two page email and lose two hours work in the process.
I reiterate that it is an extremely useful piece of software and kudos to the development team yet it would really be a pity to be abandoned for stability reasons alone especially when it was so dependable in the past.. Thank you for your time.
If 10 PCs in the same organization are all crashing, it would suggest to me that there is some external factor, such as a common security suite or network/VPN software, that is affecting TB. If it were just due to the updated TB itself, don't you think this forum would be deluged with similar complaints from the millions of users? I agree that more attention should be paid to stability, especially with major updates, but TB is more a 'developers' project' than a product aimed at consumers and businesses. So new features, needed or not, are a greater attraction for developers.
1. Debian is also a volunteers project and yet it is rock solid, reliable, dependable and production ready. So are may other projects. 2. Stability affects everyone equally be they housewives or businesses. A teenager who uses gmail and o365 is not using desktop email applications anyway. 3. Using other email applications in our setup (which btw employs no vpns or firewalls etc) shows absolutely no issues in our incumbent setup which has not changed for many years. 4. Noone seems to care enough to report crashing as I am one of the few exceptions because I am old enough to have used it for 20 years and now witness its spiral descent. 5. Older versions of TB are multiple times more stable and the new internal pgp application is everything but secure. 6. I could go on and on but if you don’t care to good faith feedback then I do rest my case.
> Noone seems to care enough to report crashing as I am one of the few exceptions because I am old enough to have used it for 20 years and now witness its spiral descent.
Thanks for reporting this. And welcome to the 20+ year club.
Let's dive in.
1. All your crash reports are version 91.2.1. We you crashing also with version 91.2.0?
2. All your crashes are reported using WIndows 10. Do you have crashes on systems other than WIndows 10?
3. You wrote "...in the last 5 years or so every update has been worse than the previous one becoming the least reliable piece ... Constant crashing ie 8-10 times a day, lack of smtp communication with the servers, and other constant issues basically make this unusable." Five years is a long time to live with that. a) please list some of your crash IDs from the version prior to 91.2.1 b) Please cite URLs to past bug reports or support request so we can take a look at your past history of issues.
4. Being on Windows you surely are running AV software. What is your AV software are you running?
we dont use AV software.
Unfortunately i have not kept any crashing records and have used various versions in the last few years in the hope of avoiding the ever so common crashing tb updates. Currently I went back to 68 and the crashing was consistently high as well but has lessened only after I stopped all notifications even though it still crashes every now and then. In parallel we are using Outlook and eM yet none of these applications crashes, ever.
I will collect as much data as I can for you as I am committed to getting to the bottom of this. If the crashes are associated with Win 10 as you imply then this still presents a problem for the user unfortunately.
Unless you deleted profiles, your crash reports are still in the profile, regardless of how and when you changed or installed versions. So you will find them all at Help > Troubleshooting.
When you post the crash IDs here, please post them as text, not screen shots.
with the current profile the below. I have changed a few profiles every now and then
bp-a846de7b-2be6-4066-a5db-b084a0211031 31/10/2021, 11:13 View bp-6bd4ed2b-4189-416f-9db9-7de130211029 29/10/2021, 11:00 View bp-9be59fe5-da6b-48dc-b47c-d76240211029 29/10/2021, 10:06 View bp-9ec9ce20-ec02-4727-980c-e8c0f0211029 29/10/2021, 09:12 View bp-c4468e9e-09e5-4ca0-acdf-7dc030211029 29/10/2021, 09:12 View bp-7c36b550-da5e-446d-bc38-2a4bc0211029 29/10/2021, 09:07 View bp-f3951392-1244-4724-a899-a3cf70211028 28/10/2021, 11:57 View bp-3459b795-35d3-4718-9162-e69d80211027 27/10/2021, 19:35 View bp-ea0f2d29-da3c-4135-8814-4a53f0211026 26/10/2021, 18:40 View bp-8118c4e9-1097-40c8-97a2-e520c0211026 26/10/2021, 18:39 View bp-03b94c8d-7c4b-40d3-97b9-bfa150211026 26/10/2021, 12:03 View bp-cfb46d1a-5346-46a4-9fe9-c5aa80211026 26/10/2021, 09:40 View bp-2b2ea9ac-b255-44cc-8b31-482860211026 26/10/2021, 08:18 View bp-5ae8be52-9fef-48b6-a93e-6658b0211025 25/10/2021, 18:10 View bp-d34ba288-6b8a-438f-ae0f-23ac50211025 25/10/2021, 17:50 View bp-7d790941-f540-44c8-91e7-0cc5f0211023 23/10/2021, 10:29 View bp-3faa4a8d-cf89-444c-9bbc-282780211022 22/10/2021, 17:14 View bp-3a22f879-15d4-4f9c-8c9e-bc3dd0211021 21/10/2021, 18:02 View bp-c8fa150b-895a-4d62-b0ad-6f98c0211021 21/10/2021, 16:47 View bp-ac4fbe54-9253-4fe2-a702-3b1d30211021 21/10/2021, 16:47 View bp-3441c078-619c-4d82-9f51-2517f0211021 21/10/2021, 15:40 View bp-7af7082b-f4ba-4202-9029-f352c0211021 21/10/2021, 15:35 View bp-5df6a8e3-53ce-4f65-9bf8-73e5e0211021 21/10/2021, 15:15 View bp-9e72cad6-1739-4d98-b448-7233e0211021 21/10/2021, 14:18 View bp-f6a9b6a4-2de2-4896-9168-e80e60211021 21/10/2021, 10:30 View bp-2e909cf0-462d-4b18-b4ec-2184a0211020 20/10/2021, 16:42 View bp-65ebc8bc-112b-4bfd-bf29-356540211019 19/10/2021, 14:25 View bp-78aaa385-1345-4a15-a787-7a0050211019 19/10/2021, 09:12 View bp-f5934e7b-5460-4a27-b868-cb4960211018 18/10/2021, 16:14 View bp-03918e00-41d6-4db8-a9a4-9b1f20211018 18/10/2021, 11:10 View bp-34e0cf79-49d2-4417-b175-d81660211015 15/10/2021, 09:14 View bp-aa4730b2-d640-4d64-942b-3c8c40211013 13/10/2021, 18:37 View bp-ef4d5eeb-13cd-4aa5-b10f-95e650210917 17/09/2021, 14:38 View bp-1ace7023-4679-474f-99af-33f020210811 11/08/2021, 11:43 View bp-336398e2-d325-4659-a1ad-14c5d0210621 21/06/2021, 13:46 View bp-da9d7860-d020-4215-8886-b80980210621 21/06/2021, 13:41 View bp-614753c2-bb06-4eb6-9655-ec3d40210519 19/05/2021, 07:33 View bp-0a234c26-5878-4d31-89c8-d801f0210512 12/05/2021, 16:54 View bp-40efccbb-5478-4b05-a3f1-f740f0210416 16/04/2021, 15:43 View bp-50aa7c39-38ad-4af0-9914-952e90210414 14/04/2021, 13:18 View bp-33c67eba-f1e2-4496-b5f2-11dfe0210331 31/03/2021, 14:28 View bp-f8594aa7-5fa4-4a23-8e4f-a49990201208 08/12/2020, 10:11 View bp-65786310-7cf7-43ad-829d-858c40201125 25/11/2020, 15:42 View
Every year I run into 5-10 people that just crash continuously. It is rare, so I guess you are unlucky in that respect. The good news is that you are crashing frequently enough that if we change something that contributes to the cause then we will probably know within a day that we've hit something good.
The variety of crash signatures suggests memory is being corrupted. To start, if you can swing it one two different PC, on one in preferences try disabling global search under "Indexing", and on another disable message sync in account settings "Sync and storage". Where possible I'd prefer to see more crash reports where Thunderbird is running in safe/troubleshoot mode.
Please describe your general environment, and types of email you receive. Are all the crashes random, i.e. don't coincide by a specific action by the user? And if you don't mind, why no antivirus?
Once I have disabled the notifications last week the crashes have been limited to a few a day so this definitely helped. I have disabled the indexer as well up to now hasn’t helped much, still crashes. Will also try to work with safe mode and see where we stand but before when I have had the chance to try this step, it had absolutely no effect in limiting crashing.
The emails are almost always plain-no images, we use html, commonly with attachments. The most common cause of triggering a crash is upon trying to open a large email of say 15-20 mb and also upon viewing in rapid succession various emails. This has a tendency to overwhelm it leading to a crash. This was not the case in the past when you could do anything to TB and would never crash. We do not store emails locally (and hate cloud email services due to privacy!!).
Not using AV as they are extremely demanding on resources, slowing everything down and leading to more complications. We are reliant on win 10 protection.
Furthermore I am using a second PC win 10-tb 92 which is equally prone to crashing albeit less frequently probably due to much less use. So perhaps equally unstable to our setup. Is there any chance that communication per se with the imap server is making it crash? Any settings to make it less sensitive to the server (ssl et al?) Will try to use gmail as server as well and see if it crashes
Ah, this little nugget is great, "trying to open a large email of say 15-20 mb and also upon viewing in rapid succession various emails". I've communicated with a couple people (but not recently) who have provided the same information.
So yes, I think your issue is imap related. And it's likely there is more than one bug.
imap unfortunately has several structural issues, but they are being chipped away. 91.2.1 for example had a major patch.
I'd really like to have your situation in a bug report so we can more easily correlate it to other issues, and because it is a great test case. Can you file it at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird please? Please include a link to this support topic.
nchrysanthou, do you have a number for your bug report?
Also, when posting an update please distinguish which computer is crashing (i.e. describe them separately) so there is a distinct record we can follow.
A sampling of your crashes...
https://crash-stats.mozilla.org/report/index/a846de7b-2be6-4066-a5db-b084a0211031 68.121 [@ memcpy | NS_CopySegmentToBuffer ]
https://crash-stats.mozilla.org/report/index/9be59fe5-da6b-48dc-b47c-d76240211029 68.12.1 [@ nsImapProtocol::HandleMessageDownLoadLine ]
https://crash-stats.mozilla.org/report/index/c4468e9e-09e5-4ca0-acdf-7dc030211029 68.12.1 [@ _invalid_parameter ] FIXED bug 1216951
https://crash-stats.mozilla.org/report/index/f3951392-1244-4724-a899-a3cf70211028 91.2.1 [@ arena_t::DallocSmall | je_free | nsImapGenericParser::AdvanceToNextToken ] https://bugzilla.mozilla.org/show_bug.cgi?id=1581766
https://crash-stats.mozilla.org/report/index/cfb46d1a-5346-46a4-9fe9-c5aa80211026 91.2.1 [@ arena_t::DallocSmall | je_free | nsImapGenericParser::ResetLexAnalyzer ]
https://crash-stats.mozilla.org/report/index/3faa4a8d-cf89-444c-9bbc-282780211022 91.2.1 [@ arena_dalloc | arena_t::RallocSmallOrLarge | BaseAllocator::realloc | je_realloc | nsMsgLineStreamBuffer::ReadNextLine ]
https://crash-stats.mozilla.org/report/index/ac4fbe54-9253-4fe2-a702-3b1d30211021 91.2.1 [@ nsImapServerResponseParser::msg_fetch] https://bugzilla.mozilla.org/show_bug.cgi?id=1333031
https://crash-stats.mozilla.org/report/index/2e909cf0-462d-4b18-b4ec-2184a0211020 91.2.1 [@ strlen | nsImapServerResponseParser::msg_fetch ] https://bugzilla.mozilla.org/show_bug.cgi?id=1333031
Tried to duplicate the issue when quickly opening a long list of emails with attachments and, so far, haven't seen a crash.
1. I think you are saying your messages are just stored on server and you don't use TB's feature to store messages for offline use?
2. Is TB set to show attachments inline?
3. Above you mention Debian project. Have you seen the crashes with TB on linux too? (Not sure if you run linux.)
4. Can you pinpoint an email that consistently crashes when opened in TB? If so, could you provide it somehow?
5. What is the type/vendor of your imap server, e.g., dovecot, gmail, exchange etc.
6. A user who was also not using offline store was having problems saving emails with huge attachments. I don't think this is also your issue but a partial solution was to set mail.server.default.mime_parts_on_demand to true. (The default on this changed to false with the pgp feature introduction which I don't know if you are using.) See https://bugzilla.mozilla.org/show_bug.cgi?id=1673093