Email search crashes [@ memcpy | nsTArray_Impl<mozilla::plugins::PStreamNotifyParent*, nsTArrayInfallibleAllocator>::AppendElements<mozilla::plugins::PStreamNotifyParent*>(mozilla::plugins::PStreamNotifyParent* const*, unsigned int) ]

NEW
Unassigned

Status

SeaMonkey
MailNews: General
--
critical
4 years ago
3 years ago

People

(Reporter: tk, Unassigned)

Tracking

({crash})

SeaMonkey 2.29 Branch
x86
Windows 7
crash

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1
Build ID: 20140612174402

Steps to reproduce:

1. Right-click on a certain folder (contains 18395 messages, no subfolders, with other folders the bug does not appear).
2. Choose "Search messages..."
3. Search with "From" field, "contains", and any search term. Same search term used with the "Subject" field, does not produce the bug. 
4. Click on "Search". 


Actual results:

Seamonkey crashes after a moment of searching.


Expected results:

Seamonkey should have shown a list of messages that have the search term in the "From" field. 

I went back to Seamonkey version 2.26.1 and the same steps as described above do not make Seamonkey crash, but instead the desired respective list of messages is produced.

Comment 1

4 years ago
Are the crashes logged (about:crashes) & if so their URLs?

So it was with SeaMonkey 2.29 where the crash started?
Does SeaMonkey 2.30 also crash?

(May want to test using a backup of your Profile rather then switching back & forth between versions in your regular Profile.)

Comment 2

4 years ago
tk: Did the mozilla crash reporter start up?
Did you allow it to send crash reports to the crash-stats server at mozilla?
Go to about:crashes. The links you see there are clickable. Please paste the most recent links in about:crashes in a comment here.
Flags: needinfo?(tk)
Keywords: crash
(Reporter)

Comment 3

4 years ago
(In reply to Philip Chee from comment #2)
> tk: Did the mozilla crash reporter start up?
IIRC, yes it did.

> Did you allow it to send crash reports to the crash-stats server at mozilla?
Again, IIRC, I did. 

> Go to about:crashes. The links you see there are clickable. Please paste the
> most recent links in about:crashes in a comment here.
http://crash-stats.mozilla.com/report/index/bp-816da72f-ab52-4655-adb7-9ac2a2141030
http://crash-stats.mozilla.com/report/index/bp-c4e04956-daa7-4dd9-abaf-2e2762141030

I hope this helps.
Flags: needinfo?(tk)
(Reporter)

Comment 4

4 years ago
(In reply to therube from comment #1)
> So it was with SeaMonkey 2.29 where the crash started?
> Does SeaMonkey 2.30 also crash?
I don't think I ever used 2.29. It seems I upgraded from 2.26 to 2.30.

The last crash reports are all from 2.30. 

> (May want to test using a backup of your Profile rather then switching back
> & forth between versions in your regular Profile.)
Hmmh, my profile does not seem broken, as it still works with the 2.26 version. 
Also, this does not strike me as a bug that seems related to the profile. I could be wrong, of course.
(Reporter)

Comment 5

4 years ago
Sorry, if I indeed reported the bug for 2.29 then I'm 100% certain it did appear in 2.29. For some reason, however, there don't seem to be any crash reports from 2.29.

Comment 6

4 years ago
Implicated bugs:
Bug 966705 Replace ParsedHeader with nsCOMArray<msgIAddressObject>
Bug 450881 nsCOMArray: Helpers for XPIDL-based arrays? [array, size_is(count)] in/out nsIFoo fooObjects]
Bug 842632 Improve the nsIMsgHeaderParser interface
Status: UNCONFIRMED → NEW
Crash Signature: [@ memcpy | nsTArray_Impl<mozilla::plugins::PStreamNotifyParent*, nsTArrayInfallibleAllocator>::AppendElements<mozilla::plugins::PStreamNotifyParent*>(mozilla::plugins::PStreamNotifyParent* const*, unsigned int) ]
Ever confirmed: true

Updated

4 years ago
Summary: Email search crashes → Email search crashes [@ memcpy | nsTArray_Impl<mozilla::plugins::PStreamNotifyParent*, nsTArrayInfallibleAllocator>::AppendElements<mozilla::plugins::PStreamNotifyParent*>(mozilla::plugins::PStreamNotifyParent* const*, unsigned int) ]
(Reporter)

Comment 7

3 years ago
This problem still persists with version 2.33.1.

Should it have been addressed by now?

I have now located the specific mail folder that causes the crash. 

I'd stay with 2.26 but its browser component is becoming outdated as it is being flagged by websites to be too old.

Comment 8

3 years ago
Eh, I've missed this one. Possible duplicate of MailNews bug 1123379 which has a couple of other crash reports listed for reference. Also, there is a recent thread on MozillaZine on an instance, see http://forums.mozillazine.org/viewtopic.php?f=40&t=2938787
Severity: normal → critical

Updated

3 years ago
Crash Signature: [@ memcpy | nsTArray_Impl<mozilla::plugins::PStreamNotifyParent*, nsTArrayInfallibleAllocator>::AppendElements<mozilla::plugins::PStreamNotifyParent*>(mozilla::plugins::PStreamNotifyParent* const*, unsigned int) ] → [@ memcpy | nsTArray_Impl<mozilla::plugins::PStreamNotifyParent*, nsTArrayInfallibleAllocator>::AppendElements<mozilla::plugins::PStreamNotifyParent*>(mozilla::plugins::PStreamNotifyParent* const*, unsigned int) ] [@ memcpy | nsTArray_Impl<T>::AppendElem…
You need to log in before you can comment on or make changes to this bug.