30319 - Changing newsgroups causes hang

Status: VERIFIED DUPLICATE of bug 29808

(MailNews Core :: Backend, defect, P3)

Description

[Kenneth J. Dowling]

This problem appeared with the 3/2 linux builds and continues in 3/3...

When changing newsgroups from one that had unread message, that have now been
read, to another newsgroup, there is a hang as the CPU usage maxs out and the
process never completes (You can still use the menus to exit, though).  If,
instead of clicking on another newsgroup, you close the mail/news window and
then reopen it, you can then click on another newsgroup without seeing the problem.

I also don't see this problem when going from a newsgroup that didn't have
unread messages, to another.

Comment 1

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

accepting bug.  I'll start investigating.

Comment 2

[Kenneth J. Dowling]

I'm also seeing this when chaging from my INBOX (UW Imap) that had unread, and
just read, messages to a newsgroup.

It looks like it might be network related. I've just discoved that this doesn't
happen if my internet connection is direct (ppp). It only happens when I'm
running through my socks server/firewall. BUT, I've ALWAYS gone through the
socks and proxy server/firewall, and have not seen this problem until the 3/2
builds.

Comment 3

[Kenneth J. Dowling]

Now I'm seeing this while connected via ppp. I still think it migth be network
related though. My connection seems rather haphazard right now, lots of lost
packets.

Comment 4

[Richard Zach]

Is Mozilla really hung?  Try Alt-Tab away from Mozilla and back.  Might be the
same problem I reported in bug 29808.

Comment 5

[Kenneth J. Dowling]

I don't think this is the same thing, although I have seen what that bug
mentions. In this case, mozilla isn't locked up. There is one process spinning
that has the cpu usage pegged. Tabbing to another window and back doesn't change
it. The window itself redaws, but in the same state. Clicking on any of the ui
does nothing. The only thing that works, is the menu. Closing the window doesn't
exit that process that's still churning away, although the window is closed.

Opening the mail/news window back up, and clicking on a newsgroup, will change
the window title, but nothing else happens. And that one process is still
spinning in the background. Quitting from mozilla closes down the process on
exiting, and without any type of error message. webshell goes back to 0.

Comment 6

[Kenneth J. Dowling]

The more I play with this, the more it does look like that other bug report.
Just now I clicked the [Stop] button and recieved and Unknown Error message box.
The cpu usage dropped back to normal, and the ui again is responsive. Although
acting very stange. And, when in that state, clicking on any newsgroup, did
change the window title, but that's all.

I can reproduce this every time, by going from a newsgroup that had unread
messages, that I just read, to another newsgroup. BUT only if that newsgroup I
just read, had not been opened/loaded in the current session yet.

Comment 7

[Kenneth J. Dowling]

Ok, this is that other bug. Alt tabbing away and back is updating the window to
whatever was previously clicked on. But, it is definately reproducable here, as
I described.

Comment 8

[Kenneth J. Dowling]

I'm no longer seeing this with 2000030316. Or at least I haven't seen it yet in
the 30 minutes I've been using it.

Comment 9

[lchiang]

Seth - do you want to mark this a dup of the other bug?

Comment 10

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

marking a duplicate.

ken / zach:  if either of you have time, can you find a 100% predictable way to
reproduce #29808

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

Comment 11

[lchiang]

verified duplicate.

The reason Seth asks is that the other bug may not get fixed for Beta1 unless a 
100 percent reproducible case can be found :-(