Paul B. Gallagher wrote:
chicagofan wrote:
WLS wrote:
chicagofan wrote:
For the second time, I am having a problem with ONE newsgroup not
loading. It's the same newsgroup and when I click to open it, TWO
applications of the news server appear in my Task Manager and it
consumes 100% of the CPU... and can not load.
The last time this happened I just gave up, subscribed again and reset
all of my filters, which happens to be quite a job in that ng. Is there
anything I can do to get around whatever is happening... or does anyone
have any idea WHAT is happening? TIA.....
bj
Did you try right clicking on the newsgroup, select properties and then
click Rebuild Summary File?
No, I haven't tried that. Thanks for the suggestion. :)
Interesting. Out of curiosity, I tried it myself (had never done it
before). CPU spiked to 95-99% and stayed there for about 10 minutes,
while RAM usage spiked from 150 MB (I had a video loaded) to about 320
MB, bounced around for awhile in that general range. Finally, SM
returned to normal and I was able to read messages and browse again.
However, when it did, the unread message count in this NG was zero,
despite the presence of six unread messages (in bold). As I advanced
through them using "N," the count stayed at zero, and when I got to the
last one, "N" prompted me to go to the first unread message in my mail
inbox.
My view settings were:
Sort by: Order received, Ascending, Threaded
Messages: All
Threads: Threads with unread
When the process completed, my threads setting had been changed to
"all." After I read all unread messages, I set it back to "Threads with
unread," and all threads disappeared as they should. In the past, when
it got confused about message count, it would display some threads
containing no unread messages. And it would also advance to unread
messages in response to "N."
We'll see how long this lasts before it gets confused again.
LOL! We had the same settings, and mine reset to show ALL threads as
well. I also remembered that it probably opened easily after
rebuilding, because it had dropped *everything*... that was prior to
*that* day.
bj
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
