User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030223 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030223 I will attach an HTML e-mail message which, if i select it in the mail thread pane, Mozilla will hang. The message renders in the content pane before hanging. Reproducible: Always Steps to Reproduce:

Works for me on Linux, albeit it slow. Reporter can you do a 'strace' on your mozilla binary to see what's happening or even gdb with the binary and process id and then a stacktrace.

Ah, it seems that the nature of the bug is a little different from what i thought. The "hang" seems to happen only when i try to expand the recipient list (which is rather long) in the headers. And it's not really a hang, it just takes almost all of the CPU cycles for a while, but after a long wait, CPU cycles go back to normal. Since this bug is different, i'll search for a duplicate. I'll either change the summary line or the bug should be marked invalid. (What i'm seeing is still a bug, since it shouldn't eat all of my CPU cycles for such a long time just to parse/render the recipient list.) But... just in case this bug is not invalid, i'll attach the strace. I don't have any experience with either gdb or strace. So, if you need something more than what i'm attaching, please give me explicit instructions (with any flags i need to know about).

Changing summary from "viewing this e-mail message hangs Mozilla" to "expanding long recipient list slow and hogs CPU cycles", until i have time to see whether this bug is a duplicate of something else.

So this is a followup bug to bug 64764.

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.