Closed Bug 22238 Opened 25 years ago Closed 25 years ago

Crash when clicking on a message

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

x86
Other
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 22001

People

(Reporter: scottputterman, Assigned: chuang)

Details

This is a random crash that just happened on this morning's release build and that I couldn't reproduce when I clicked on the same message. I had just sent a message to the mail-news newsgroup. I clicked the GetMsg button and then clicked on the message when the header showed up. Then I crashed with this stack that I got from talkback Incident ID: 2780751 nsAddrDatabase::GetCardForEmailAddress [d:\builds\seamonkey\mozilla\mailnews\addrbook\src\nsAddrDatabase.cpp, line 2683] IMGlue.dll + 0xe0f5 (0x01ebe0f5) aimstat.dll + 0x1959 (0x03441959) nsMimeXULEmitter::ProcessSingleEmailEntry nsMimeXULEmitter::OutputEmailAddresses nsMimeXULEmitter::WriteEmailAddrXULTag nsMimeXULEmitter::WriteXULTag nsMimeXULEmitter::OutputGenericHeader nsMimeXULEmitter::DumpSubjectFromDate nsMimeXULEmitter::Complete nsStreamConverter::OnStopRequest These are the values of all of the variables in GetCardForEmailAddress: this = 0x032fa930 (*this) = Data not available directory = 0x04314e98 (*directory) = Data not available emailAddress = 0x0012fa18 (*emailAddress) = 1953457011 (0x746f6373) cardResult = 0x0012fa80 (*cardResult) = 0x00000000 (*(*cardResult)) = Data not available emailAddressYarn = {mdbYarn} mYarn_Buf = 1243672 (0x0012fa18) mYarn_Fill = 20 (0x00000014) mYarn_Size = 20 (0x00000014) mYarn_More = 2147483648 (0x80000000) mYarn_Form = 0 (0x00000000) mYarn_Grow = 0x60b97c58 (*mYarn_Grow) = Data not available outRowId = {mdbOid} mOid_Scope = 20 (0x00000014) mOid_Id = 64 (0x00000040) rv = 0 (0x00000000) cardRow = 0x0012fa80
I've actually crashed two other times in the same spot on different messages according to talkback reports: Incidents 2780753 and 2780754
Summary: Crash when clicking on news message → Crash when clicking on a message
In case this isn't a dup, this is pretty common. I checked talkback and there are at least 20 reports filed with the same crash from today.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 22001 ***
Status: RESOLVED → VERIFIED
Mark it verified/dup.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.