Closed Bug 1056290 Opened 10 years ago Closed 8 years ago

bulk select all messages and mark "not junk", multiple "Unresponsive Script", then null pointer crash in nsISupports** nsTArray_Impl<nsISupports*, nsTArrayInfallibleAllocator>::AppendElements<nsISupports*>

Categories

(Thunderbird :: General, defect)

All
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bc, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-76dd55f1-b8b7-467c-bd34-a4eda2140820. ============================================================= 1. Select all messages in a folder (in my case 4000+) 2. Right click message list 3. Select Mark as Not Junk 4. If needed allow execution if the slow script dialog fires. 5. Crash Reproducible. See also bp-8dd81cab-db2f-4066-a49c-57ec12140820
Crash Signature: [@ nsISupports** nsTArray_Impl<nsISupports*, nsTArrayInfallibleAllocator>::AppendElements<nsISupports*>(nsISupports* const*, unsigned long)] → [@ nsISupports** nsTArray_Impl<nsISupports*, nsTArrayInfallibleAllocator>::AppendElements<nsISupports*>(nsISupports* const*, unsigned long)] [@ nsISupports** nsTArray_Impl<T>::AppendElements<T>]
bp-8dd81cab-db2f-4066-a49c-57ec12140820 is unfortunately long gone. Some rare linux crashes are still reported such as bp-3684611f-3628-46ff-8d2f-f71a32160819 but the stack not instructive, and none newer than version 36. The performance symptoms are like bug 837530 and bug 693659. The crash perhaps was related to running out of memory - like bug 610551 and bug 583365. I tested a folder selecting 6k messages and picked "not junk". Memory went up by 100MB but otherwise no ill effects. So => WFM. (FTR, a fix for bulk marking was done in version 17 via bug 471492. - but that predates this bug report - unless you were running a very old version of Thunderbird when you reported the bug.) If you can still reproduce this, please post an update
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Summary: null pointer crash in nsISupports** nsTArray_Impl<nsISupports*, nsTArrayInfallibleAllocator>::AppendElements<nsISupports*>(nsISupports* const*, unsigned long) → bulk select all messages and mark "not junk", multiple "Unresponsive Script", then null pointer crash in nsISupports** nsTArray_Impl<nsISupports*, nsTArrayInfallibleAllocator>::AppendElements<nsISupports*>
You need to log in before you can comment on or make changes to this bug.