Mail/News hangs on startup if inbox contains a message that contains japanese characters



MailNews: Message Display
14 years ago
12 years ago


(Reporter: Michael Neilly, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029

I was forwarded an email (confidential so I can't include it)
that contains japanese characters. On 1.5 is hangs if the messages
is selected. On 1.6a, Mail/News hangs on startup before "painting"
any of the windows. I get a border and garbage in a hung window.

It's one thing when 1.5 hangs. I can tell what message was the
offender and not try to open it after restarting. I can't even
run 1.6a if someone chooses to send me such mail....

Reproducible: Always

Steps to Reproduce:
1. Send yourself an email containing japanese characters
2. Open Mail/News
3. Watch it hang

Actual Results:  
hung Mail/News

Expected Results:  
No hang

Comment 1

14 years ago
Is this still an issue in recent builds?
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail

Comment 2

13 years ago
I see the same problem in mozilla 1.7.5 (on RedHat 9 as well as on
White Box Linux). I was under the impression it was Chinese characters
rather than Japanese, but I may be wrong there.

I find that it hangs up
- when I receive mail that contains the characters
- when I try to open a newsgroup that does
- when I try to open an existing message in another mail folder that does.

The least invasive solution I found is to "kill -9" the browser.
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:
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.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.