*** observed with 2002-04-23 branch build and localized ja build*** This bug happens somehow only with iso-2022 (i tried other ja and chinese encodings and they are fine). This is especially visible for localized builds where the default encoding is iso-2022. Steps to reproduce: -add news.mcom.com ; -subscribe to a russian newsgroup (say kherson.commerce, this one i just know is huge and has mostly no-mime headers;) - download all messages; - you'll see the headers displayed blank; - try to scroll, you'll crash PS. i don't crash when i scroll in the folder with 10-15 messages, this newsgroup has~ 500
Please attach talkback info.
Status: NEW → ASSIGNED
Keywords: crash, nsbeta1
actually i have to reframe my comments: the application gets frozen, doesn't crash so no talkback..
Summary: Changing folder properties to japanese-ISO-2022 turns nomime headres blank/scrolling crash → Changing folder properties to japanese-ISO-2022 turns nomime headres blank/freeze on scrolling
impact language users: all japanese users 52.1M 9.2% of internet users visibility- HIGH, in major functional area- we will freeze in mail OR news severity- HIGH, hang when we hit that problem this is a [adt1] bug. roy- please help to figure out why we are hang here. nhotta is busy for other adt1 bug now.
Assignee: nhotta → yokoyama
Status: ASSIGNED → NEW
Keywords: nsbeta1 → nsbeta1+
Let's see what I can do.
Target Milestone: --- → mozilla1.0
There is another bug (bug 134694) filed for the blank problem. On bug 134694, please see Naoki's comments #11.
and another one that i forgot to mention: bug# 91682 (setting folder charset to UTF-8 has the same effect)
when i say "the same effect" i mean : no-mime headers are blank and the application hangs after scrolling.
Summary: Changing folder properties to japanese-ISO-2022 turns nomime headres blank/freeze on scrolling → Changing folder properties to japanese-ISO-2022/or to UTF8 turns nomime headres blank/freeze on scrolling
Created attachment 80967 [details] Stack trace of infinite loop Hang doesn't occure at first. You have to scroll few pages down. I think one of newsgroup posting is a cause of this problem.
bug 132583 is about infinite loop problem in NS_ConvertUTF8toUCS2, but the caller should avoid generating illegal UTF-8
Roy,when you say in your comment #8 that there is a specific posting that causes a problem do you mean a specific article in kherson.commerce? I've seen the same hang in relcom.cinema with the folder charset set to iso-2022ja or utf8.
>there is a specific posting that >causes a problem do you mean a specific article in kherson.commerce? Yes, but I failed to pin point which one(s) >I've seen the same hang in relcom.cinema with the folder charset set to >iso-2022ja or utf8. It is entirely possible of having the same infinite loop.
Roy,actually you might be right about a specific newsarticle after all,there is no hang with a huge chinese newsgroup tw.bbs.comp.linux, unfortunately when the hang happens with russian newsgroups and if at the time of the hang you had only one mail account such as news then this account is gone! you have to add it again...
Created attachment 81070 [details] [diff] [review] Populate the unicode string with replacement char in case of decoder failure This is one of the smallest change, I can think of, to fix this bug. (I'd like to minimize the amount of the code changes before the release) nhotta: can you review?
Comment on attachment 81070 [details] [diff] [review] Populate the unicode string with replacement char in case of decoder failure r=nhotta
Attachment #81070 - Flags: review+
*** Bug 139954 has been marked as a duplicate of this bug. ***
Comment on attachment 81070 [details] [diff] [review] Populate the unicode string with replacement char in case of decoder failure sr=bienvenu
Attachment #81070 - Flags: superreview+
Comment on attachment 81070 [details] [diff] [review] Populate the unicode string with replacement char in case of decoder failure a=asa (on behalf of drivers) for checkin to the 1.0 branch
Attachment #81070 - Flags: approval+
checked into the trunk. ji: please verify the bug tomorrow. thanks
Severity: - Hang when simply scrolling mail headear Impact Analysis: - mail/news only fix - no impact on Western encoding (since intl_is_utf8() returns True)
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
QA contact to marina. Marina, could you check this on tomorrow's trunk build. Thanks.
QA Contact: ji → marina
tested with 2002-04-30-10 trunk build, it is fixed, there is no freeze neither hang after changing folder properties and scrolling.
adding adt1.0.0 keyword Severity: - Hang when simply scrolling mail headear Impact Analysis: - mail/news only fix - no impact on Western encoded mail (since intl_is_utf8() returns True)
Please get the bug VERIFIED and then re-nominate.
syd: oops, i thought marina did it already. (comment #21) marina: please verify.
in my comments #21 i said that this is fixed in the trunk, i was waiting for the branch build to mark it "verified"
verified on the trunk
Status: RESOLVED → VERIFIED
add adt1.0.0 keyword
adt, please consdier taking this. It is very likly to hang by this for Japanese users using mail or newsgroup. When the uers view mail or news, it will hang if the message does not include a mime charset but have 8 bits data.
adt1.0.0+ (on ADT's behalf) approval for checkin to the 1.0 brnach. Pls check this in today, then add the fixed1.0.0 keyword.
Keywords: adt1.0.0 → adt1.0.0+
Whiteboard: [adt1] → [adt1] [ETA 05/03]
fix checked into the branch (keyword 'fixed1.0.0 added)
You need to log in before you can comment on or make changes to this bug.