Closed Bug 557243 Opened 16 years ago Closed 15 years ago

crash [@ nsACString_internal::Finalize()] - [@ nsImapProtocol::Capability]

Categories

(MailNews Core :: Networking: IMAP, defect)

Product:
MailNews Core
Component:
Networking: IMAP
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: wsmwk, Unassigned)

Details

(Keywords: crash)

Crash Data

crash [@ nsACString_internal::Finalize()] - [@ nsImapProtocol::Capability] looks rare bp-fd9a53a2-147d-4663-bfd1-db5462100321 0 @0xf160812b 1 xpcom_core.dll nsACString_internal::Finalize xpcom/string/src/nsTSubstring.cpp:205 2 mozcrt19.dll arena_dalloc_small objdir-tb/mozilla/memory/jemalloc/src/jemalloc.c:4102 3 mozcrt19.dll free objdir-tb/mozilla/memory/jemalloc/src/jemalloc.c:6012 4 xpcom_core.dll nsACString_internal::Finalize xpcom/string/src/nsTSubstring.cpp:205 5 thunderbird.exe nsImapProtocol::Capability mailnews/imap/src/nsImapProtocol.cpp:5284 6 thunderbird.exe nsImapProtocol::ProcessCurrentURL mailnews/imap/src/nsImapProtocol.cpp:1695 another crash is nsImapProtocol::HandleIdleResponses bp-15a03766-9d9f-4e57-a0ca-ce8472100317 .... needs a separate bug?
those both look like memory/heap corruptions, so it's quite possible they have the same cause.
nsACString_internal::Finalize() no longer exists starting with v3.1.7. and also not seen on trunk. either morphed or gone. so closing
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Crash Signature: [@ nsACString_internal::Finalize()] [@ nsImapProtocol::Capability]
You need to log in before you can comment on or make changes to this bug.