77625 - Reloading a news article gets strange results

Status: VERIFIED DUPLICATE of bug 76558

(MailNews Core :: Networking: NNTP, defect)

Description

[ji]

*****Observed with linux, win32 trunk build*****

When selecting charset menu on a news article gets unexpected results.
If it's an ascii article, after selecting the menu, the mail body displays the
view message source results, but in a long string w/o line break. If it's a
Japanese article, it gets a download window. All these only happens once at the
first time when you do select charset menu action to the article. When you do
the same thing the second time, it goes back to normal.

Steps to reproduce:
1. Select a news article.
2. Select View | Character Encoding.. | <any encoding>

Comment 1

[ji]

Attachment: A screen shot showing the result of selecting charset menu to an ascii article

Comment 2

[nhottanscp]

Adding putterman to cc, any news related changes recently?

Comment 3

[ji]

Did more testing on this. This happens when reloading news article.
To see it, just select View | Reload.
Since selecting a charset reloads the article, so I saw this with selecting the 
charset menu too.

Comment 4

[ji]

Viewing message source to a news article gets similiar results:
to an ascii article, "view message source" displays the info in a long string 
w/o line breaks in the seperate view source window.
to a non-ASCII article, "view message source" gets a download window.

Comment 5

[ji]

Marina has reported view message source problem in bug 77449.

Comment 6

[scottputterman]

cc'ing sspitzer

Comment 7

[nhottanscp]

Reassign to putterman.
This is reproducible with ASCII news message by "View -> Reload".

Comment 8

[scottputterman]

reassigning to sspitzer

Comment 9

[(not reading, please use [e-mail] instead)]

this is probably another bug caused by some memory cache badness.

I've got several bugs that I believe are caused by this.

see #76436 and #76558, I'm sure there are more.

adding this to my list, I hope to investigate tomorrow.

Comment 10

[scottputterman]

As Seth said, this looks to be a dup of 76558 to me so marking it that way.

*** This bug has been marked as a duplicate of 76558 ***

Comment 11

[laurel]

Marking verified as a duplicate.