Closed Bug 658862 Opened 14 years ago Closed 14 years ago

Crash when forwarding S/MIME encrypted message [@ mime_find_class ], [@ mime_find_class(char const*, MimeHeaders*, MimeDisplayOptions*, int)]

Categories

(MailNews Core :: MIME, defect)

x86
All
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 6.0

People

(Reporter: patrick, Unassigned)

References

Details

Steps to reproduce: 1. Send yourself a S/MIME encrypted message 2. Use Message > Forward as attachment with the message from (1) 3. Send the message
See also bug 658793.
Sorry, forgot to add the crash information. Crash IDs: 5ee1042a-1be7-44df-b67f-a174e2110522 fd0b399b-d4b9-4640-8017-adc112110522 Stack: 0 XUL mime_find_class mimei.cpp:754 1 XUL mime_crypto_object_p mimei.cpp:1194 2 XUL MimeMessage_parse_line mimemsg.cpp:399 3 XUL mime_LineBuffer mimebuf.cpp:184 4 XUL MimeObject_parse_buffer mimeobj.cpp:275 5 XUL mime_display_stream_write mimemoz2.cpp:991 6 XUL nsStreamConverter::OnDataAvailable nsStreamConverter.cpp:979 7 XUL nsMailboxProtocol::ReadMessageResponse nsMailboxProtocol.cpp:586 8 XUL nsMailboxProtocol::ProcessProtocolState nsMailboxProtocol.cpp:683 9 XUL nsMsgProtocol::OnDataAvailable nsMsgProtocol.cpp:387 10 XUL nsInputStreamPump::OnStateTransfer nsInputStreamPump.cpp:510 11 XUL nsInputStreamPump::OnInputStreamReady nsInputStreamPump.cpp:400 12 XUL nsInputStreamReadyEvent::Run nsStreamUtils.cpp:114 13 XUL nsThread::ProcessNextEvent nsThread.cpp:618 14 XUL NS_ProcessPendingEvents_P nsThreadUtils.cpp:200 15 XUL nsBaseAppShell::NativeEventCallback nsBaseAppShell.cpp:130 16 XUL nsAppShell::ProcessGeckoEvents nsAppShell.mm:399 17 CoreFoundation __CFRunLoopDoSources0 18 CoreFoundation __CFRunLoopRun 19 CoreFoundation CFRunLoopRunSpecific 20 HIToolbox HIToolbox@0x2e7ed 21 HIToolbox HIToolbox@0x2e550 22 HIToolbox HIToolbox@0x2e4ab 23 AppKit _DPSNextEvent 24 AppKit -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 25 AppKit -[NSApplication run] 26 XUL nsAppShell::Run nsAppShell.mm:746 27 XUL nsAppStartup::Run nsAppStartup.cpp:218 28 XUL XRE_main nsAppRunner.cpp:3754 29 thunderbird-bin main nsMailApp.cpp:104 30 thunderbird-bin thunderbird-bin@0xb83
Depends on: 243833
stacks don't match up perfectly, but I would think this windows signature is the same crash ... mime_find_class(char const*, MimeHeaders*, MimeDisplayOptions*, int) bp-1a92b2b2-1df7-49b4-8114-78aec2110502 0 thunderbird.exe mime_find_class mailnews/mime/src/mimei.cpp:817 1 thunderbird.exe mime_create mailnews/mime/src/mimei.cpp:884 2 thunderbird.exe MimeMessage_close_headers mailnews/mime/src/mimemsg.cpp:461 3 thunderbird.exe MimeMessage_parse_line mailnews/mime/src/mimemsg.cpp:277 4 thunderbird.exe convert_and_send_buffer mailnews/mime/src/mimebuf.cpp:184 5 thunderbird.exe mime_LineBuffer mailnews/mime/src/mimebuf.cpp:272 6 thunderbird.exe MimeObject_parse_buffer mailnews/mime/src/mimeobj.cpp:275 7 thunderbird.exe mime_display_stream_write mailnews/mime/src/mimemoz2.cpp:944 8 thunderbird.exe nsStreamConverter::OnDataAvailable mailnews/mime/src/nsStreamConverter.cpp:979 9 thunderbird.exe nsMailboxProtocol::ReadMessageResponse mailnews/local/src/nsMailboxProtocol.cpp:586 10 thunderbird.exe nsMailboxProtocol::ProcessProtocolState mailnews/local/src/nsMailboxProtocol.cpp:683 11 thunderbird.exe nsMsgProtocol::OnDataAvailable mailnews/base/util/nsMsgProtocol.cpp:359
OS: Mac OS X → All
Summary: Crash when forwarding S/MIME encrypted message [crash @mime_find_class ] → Crash when forwarding S/MIME encrypted message [@ mime_find_class ], [@ mime_find_class(char const*, MimeHeaders*, MimeDisplayOptions*, int)]
Component: General → MIME
Product: Thunderbird → MailNews Core
QA Contact: general → mime
this should have been fixed by backing out the fix for bug 243833, on both trunk and miramar builds. If you're still seeing this crash, then it wasn't caused by the fix for bug 248833.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Flags: in-testsuite-
Target Milestone: --- → Thunderbird 6.0
You need to log in before you can comment on or make changes to this bug.