Closed Bug 614026 Opened 15 years ago Closed 15 years ago

crash if i want to download a message via IMAPS

Categories

(MailNews Core :: Networking: IMAP, defect)

1.9.2 Branch
x86_64
Windows 7
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: burnjack, Unassigned)

References

()

Details

(Keywords: crash, qawanted, stackwanted, Whiteboard: [closeme 2011-03-15])

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ImageShackToolbar/5.2.4 Build Identifier: 3.1.6 While i retrieve this E-Mail (http://www.burnzone.de/up/mail.txt) which is created by the backupscript backup2l my TB crashes or need a long time to load the message. Reproducible: Always Steps to Reproduce: 1. upload this message to your mailserver http://www.burnzone.de/up/mail.txt 2. Try to download the mail via IMAP(S) 3. wait ... Actual Results: TB crashes or loads the message after some minutes Expected Results: Open the message in less then a 5 seconds like very other message I could download the message with Pegasus Mail without a problem
(In reply to comment #0) > Steps to Reproduce: > 1. upload this message to your mailserver http://www.burnzone.de/up/mail.txt There was no need to upload the mail. "Save as .EML, Drag&Drop the .EML file to thread pane of a local mail folder" was sufficient. When the mail is clicked, Tb 3.1.5 on Win-XP consumed 50% CPU of Core2Duo(100% if single CPU) for long time and kept unresponsive status. I closed Tb by X button after a few minutes. It's probably due to very long line, Line 76 of the mail data, 421814 bytes data + LF(0x0A). If IMAP and/or if corruption of control block unforunately happens internally, crash may happen. It looks that both of next two known problems happen at same time. - Problem when very very long line. - Severe slowness in rendering of very large text data. Crash may be relevant to next data of line 76. > Uploading srv01.26.tar.gz: (very very long data) [LF] Protocol name check may happen for string of "srv01.26.tar.gz: ...[LF]" because of ":" in a text line. By the way, next header was somehow interpreted like From: "(Cron Daemon)" <root@burnzone.de>, as sender wants. > From: root@burnzone.de (Cron Daemon) Quirks? Or RFC compliant header?
burnjack Do you still see the problem? - A stacktrace would be very helpful https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report - A testcase message attached to the bug would be very helpful
URL: http://www.burnzone.de/up/mail.txt → NA http://www.burnzone.de/up/mail.txt
Whiteboard: [closeme 2011-02-11]
(In reply to comment #3) > burnjack > > Do you still see the problem? > - A stacktrace would be very helpful > https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report > - A testcase message attached to the bug would be very helpful yes is still see this problem... - no "normal" stacktrace possible and i don't want to install the ~700-800MB Win SDK - I attached the testcase message again, see http://www.burnzone.de/up/mail.txt
thanks. please attach a short protocol log to the bug for developer and for comparison to whomever attempts to replicate your problem. Sanitize the log if needed to removed sensitive information. See https://wiki.mozilla.org/MailNews:Logging and use ImapAutoSync:5,imap:5,timestamp
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
Whiteboard: [closeme 2011-02-11]
Version: unspecified → 1.9.2 Branch
the imap.log is created while TB starts and checks my mail accounts. When i click on this message (http://www.burnzone.de/up/mail.txt) nothing happens
reporter: windbg is around 10mb, not 700mb.
you wont see the imap.log contents until after you close thunderbird. please try again for protocol log
Whiteboard: [closeme 2011-03-15]
RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: