Open Bug 610551 Opened 10 years ago Updated 4 months ago

(Thunderbird) Crash in [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ]. Mostly OOM. Often from operating on thousands of messages.

Categories

(Thunderbird :: General, defect)

defect
Not set
critical

Tracking

(Not tracked)

People

(Reporter: wsmwk, Unassigned)

References

(Depends on 4 open bugs, )

Details

(Keywords: crash)

Crash Data

+++ This bug was initially created as a clone of Bug #552909 +++

1 % of Thunderbird crash sigs are (empty signature).  Unlike Bug #552909, where firefox has about the same % of null sig crashes as Thunderbird, less than 0.5% of Firefox crashes are (empty signature).

Crash comments seem to be an equal mix of multiple reports of these networking type issues:
* going offline/online
* trying to connect to email account
* setting up an account

Plus some single reports of 
* BirdieSync bp-fa338b28-36d6-482b-91c3-057bb2101025
* sending mail
* printing

https://crash-stats.mozilla.com/report/list?version=Thunderbird:3.1.5&version=Thunderbird:3.1.4&version=Thunderbird:3.1.3&build_id=&query_search=signature&query_type=exact&query=&date=2010-10-25%2012:00:00&range_value=2&range_unit=weeks&hang_type=any&process_type=any&plugin_field=&plugin_query_type=&plugin_query=&do_query=&signature=&missing_sig=EMPTY_STRING&page=1
increased to 4%, #1 crash in v6. perhaps as a result of bug 589955.

bug 587729 and Bug 527095 themselves might not help us in most cases, but there should be offshoots that do help.

The mix of comments is substantially different from what's mentioned in comment 0 ...

most crash comments are about copying/moving/deleting 1k - 20k messages.
one mentions marking 45k messages as Not Junk

a couple about compact.
a couple about clicking inbox (corrupted folder?)

one mentions having 40k google contacts (surely OOM)
  bp-1ee40580-c634-482c-b382-e03da2110817
 and two others have gcontacts
   bp-f799ec49-b6c3-46b4-85ae-774902110824
   bp-2a2f19c4-96f6-4699-a94f-0d4282110818 

one mentions not being able to run Lion
bp-5cf22a91-a2ba-4c12-943f-9d6072110817 (liam)

one mentions crash when closing starting with version 5
bp-4a6db82d-30aa-492e-b371-534a32110817
Danish Dictionary for the Spell Checker	danish@dictionaries.addons.mozilla.org	2.1.6	current
	noia2_full_xt@gd.noia	3.30	
	{4dce973c-25a5-4657-8e37-6c2a85c24a7e}	0.9pre	
	{b243fe83-b8a7-47de-855d-21d865243d5d}	0.6.1	
	{e2fda1a4-762b-4020-b5ad-a41df1933103}	1.0b5	
	{F8147CF4-B9E3-445B-AA87-081ED66548F8}	1.6.6	
	noia2_full@gd.noia	3.30	

---------------------------------
bug 583365 about moving many messages may be OOM crash
Depends on: 587729, 527095, 583365
Summary: 1% of Thunderbird crashes contains [@ (empty signature)] → 4% of Thunderbird crashes contains [@ (empty signature)]. mostly OOM. Often from operating on thousands of messages
bug 538378 has potential to kill bug 583365, which may be the bulk of these crashes (based on crash comments)

firefox counterpart to this bug, is bug 711568
Severity: major → critical
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ] [@ (empty signature)]
Keywords: crash, topcrash
See Also: → 711568
Summary: 4% of Thunderbird crashes contains [@ (empty signature)]. mostly OOM. Often from operating on thousands of messages → 4% of Thunderbird crashes contains [@ EMPTY: no crashing thread identified; corrupt dump ], [@ (empty signature)]. mostly OOM. Often from operating on thousands of messages
Depends on: 538378
user at https://getsatisfaction.com/mozilla_messaging/topics/thunderbird_crashes_continuously#reply_8856570 was ablle to stop crashes only by creating a new profille
Depends on: 797323
Depends on: 862384
Depends on: 871926
Depends on: 1028720
currently #15 crash signature for 38.6.0, 0.6%.  

Some users also crash OOM | small, ranked #5, 1.7% of crashes. A couple examples 
* peter: bp-50f955f7-43b1-4962-9d88-f68c82160308 OOM | small   bp-35f3cf81-9f42-42a9-b382-41a592160308 EMPTY  (OS is not recorded, but Available virtual memory is cited as 4294836224)
* super: bp-97f81321-1ee2-47d1-85ca-cca4e2160313 OOM | small   bp-e53d2395-36b7-4633-88c2-f869b2160107 EMPTY (Mac)
* ozaki: bp-902dddd9-f42e-4452-bbee-bcbdb2160215 OOM | small   bp-a150c031-e984-4824-acbd-927a72160215 EMPTY (Mac)
In version 45.2.0 we are at 0.66% and #10 ranking.

As previously noted, not suprisingly, some users also crash with signature OOM | small.
https://crash-stats.mozilla.com/signature/?product=Thunderbird&signature=OOM%20%7C%20small&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#comments
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ] [@ (empty signature)] → [@ EMPTY: no crashing thread identified; corrupt dump ] [@ (empty signature)] [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ]
Depends on: 1256224
See Also: → 1256224
Depends on: 924278
Signature> EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER 

Top Crashers for Firefox 55.0a1
Top 50 Crashing Signatures. 7 days ago through 2 minutes ago. 

Top browser crasher #3.


Top Crashers for Firefox 54.0b
Top 50 Crashing Signatures. 7 days ago through 2 minutes ago. 

Top browser crasher #2.


Top Crashers for Firefox 54.0a2
Top 50 Crashing Signatures. 7 days ago through 3 minutes ago. 

Top browser crasher #1.


Top Crashers for Firefox 53.0.2
Top 50 Crashing Signatures. 7 days ago through 3 minutes ago. 

Top browser crasher #2.
See Also: → 1245570, 1360392
Summary: 4% of Thunderbird crashes contains [@ EMPTY: no crashing thread identified; corrupt dump ], [@ (empty signature)]. mostly OOM. Often from operating on thousands of messages → (Thunderbird) Crash in [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ]. Mostly OOM. Often from operating on thousands of messages.
For current thunderbird versions this ranks in the 35-50 range, so no longer topcrash
Crash Signature: [@ EMPTY: no crashing thread identified; corrupt dump ] [@ (empty signature)] [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ] → [@ EMPTY: no crashing thread identified; corrupt dump ] [@ (empty signature)] [@ EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER ] [@ EMPTY: no crashing thread identified; ERROR_NO_THREAD_LIST ]
You need to log in before you can comment on or make changes to this bug.