616814 - Subscribing a NNTP group locks up the whole application

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[plop]

User-Agent:       Mozilla/5.0 (X11; DHP; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101030 Gentoo Firefox/3.6.12
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; fy-NL; rv:1.8.1.23) Gecko/20100130 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0

I have an AMD Phenom(tm) II X4 965 Processor ... which is a pretty recent and powerfull CPU, with 4G RAM (what is not that small for 2010). Each time i subscribe to a NNTP newsgroup, TB locks up for random time. With one core at 100% when TB is not shown on screen, and all cores at 100% when the window is visible.

Reproducible: Always

Steps to Reproduce:
1. subscribe a NNTP group 

Actual Results:  
- Window content not refreshed, all TB window locked up (main, composers ... )
- locks for longer when subscribing for several groups

Expected Results:  
- at least warn it will lock-up
- warn about estimated time it will lockup
- show a progress bar
- lock-up only the main window, not the "NNTP unrelated ones" (composer, Main wins that were not used to subscribe)

With time, I have been buying more and more powerfull computers, but Mozilla products have been bigger and bigger, slower and slower. With technology, and contributors joining the Mozilla project, the stability and usability of the Mozilla products have grown DOWN. TB and Firefox crash more and more often. The bigger CPU and RAM I have, the slower they run. TB 1.0 used to be nearly fast and fluent on my old P3 800; it is NOT faster and more stable on my AMD quad 3.4GHz ...

And there are still unfixed bugs I created (or joined) more than 4y ago ... 

The team writes more code, introduces more bugs, but do not fixes already declared bugs.

Comment 1

[Joshua Cranmer [:jcranmer]]

Can you follow the steps at <https://wiki.mozilla.org/Thunderbird:Testing:Memory_Usage_Problems>? While it's mostly memory usage, some of the steps can help with CPU usage as well.

In addition, can you attempt to get stack traces of the application while it is hanging?

Comment 2

[plop]

I have 4G RAM, and 2.5G free ... so no I don't have any memory problem. And, no i won't have time to rebuild TB with debug infos; if I ever have time to dig into some bug, I have to bother first about more important apps, such as kernel locks-up, or X crashes. Because Linux and X are way more vital than TB, and, because their respective teams are really more active, and interessed in my bug reports; they care about my reports, and, when I take time to provide full logs, they use it to fix the code. While Moz team never fixed any bug I created or joined; even when logs were provided.

Amongst other things, I will never forgive the Firefox team to have introduced security breaches in FF3 ... and refuse to close them.

Comment 3

[Joshua Cranmer [:jcranmer]]

Well, if you refuse to provide help, there is no way this bug can be fixed.