The problem is that if you set up a POP account (didn’t try IMAP) to use STARTTLS (the default) against a server that does not support SSL, attempting to check mail will result in very high CPU usage (120%+ on my dual-code Macbook Pro), without any indication of what is happening. to reproduce: - Create a new POP account - Leave SSL set to STARTTLS, port 110 - Use a server that does NOT support SSL (at least not STARTTLS) - Check mail - Note you are not asked for the password (even though this is the first mail check) - Note that there is no error indicated - Note that CPU usage goes very high - Set account NOT to use SSL and mail check goes fine.
Matt can you instrument a bit and give us where we are eating all that CPU ?
Component: General → Networking
Product: Thunderbird → MailNews Core
QA Contact: general → networking
Version: 3.0 → Trunk
> Matt can you instrument a bit and give us where we are eating all that CPU ?
Whiteboard: [needs shark profile]
Hm. My ISP's mail servers, pop.belgacom.net and pop.skynet.be, don't support SSL or TLS. For quite a long time I've been aware that "TLS (if available)" didn't work, I had to set "None". That was with some earlier version of SeaMonkey where it was set by radio buttons. Now it's a rolldown widget: Edit → Mail & Newsgroups Account Settings → (server name) → Server Settings → Security Settings → Connection security: | None |v| <== | STARTTLS | | SSL/TLS | Authentication method: | Password, transmitted insecurely |v| <== | Encrypted password | | Kerberos / GSSAPI | | NTLM | | TLS Certificate | I'm using the above (on Linux) because it works. I think that it used to be the same (with radio buttons, in those days) when I was on Windows XP, but that was several years ago, my memory is fuzzy. Maybe even on Thunderbird 1.0. I haven't retested this recently. I could try, to see if the symptoms are the same on Linux as on Mac, but finding out "where we are eating all that CPU" is above my ken.
(In reply to Wayne Mery (:wsmwk) from comment #4) > see > https://developer.mozilla.org/en-US/docs/Mozilla/Performance/ > Reporting_a_Thunderbird_Performance_Problem_with_G Hm. I'm not forgetting this (and I'm intentionally not clearing the NEEDINFO) but I'm going to wait a little for the following reasons: (a) My current computer is in very bad shape. Today I could only get it to boot and remain running by selecting "Fan: Silent (minimum noise, may reduce performance)" in the BIOS setup. I've seen another computer which looks better (more max memory on the motherboard; bigger HD; hopefully a "saner" CPU; etc.; and second-hand but not third-hand AFAICT); I'm gonna buy it as soon as I have the money. (b) According to its install.rdf, the Gecko Profiler Add-On supports Firefox and Thunderbird but not SeaMonkey. It also requires the add-on SDK. Last time I booted up there was talk about adding the SDK backends to SeaMonkey but I don't know how far that project has progressed yet. Once I'm sure that SeaMonkey has the necessary backends, _and_ I have a newer computer, I'l try "converting" that add-on for use with SeaMonkey, see http://forums.mozillazine.org/viewtopic.php?f=40&t=2834855 and http://addonconverter.fotokraina.com/ Then I'll try getting mail with TLS with the add-on disabled to see if I experience the problem, and then, if I do, with the add-on enabled to gather the profiling data.
Sorry, this was 4 years ago. I long ago stopped working on this project. If I start using Thunderbird again I'll keep an eye out for the problem.
After months with no Internet, I've finally found out how to configure the Network Manager on this "new" system (well, I got the DVD at FOSDEM in February). The former box had a disk crash so no way to salvage the config. I haven't yet succeeded to get mail other than webmail yet. I installed SeaMonkey a few hours ago but AFAICT it hasn't yet asked for a mail password. Wayne, I don't think I'll be able to answer your NEEDINFO one way or another in the foreseeable future. Sorry.
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
(In reply to Matt Dudziak from comment #0) > The problem is that if you set up a POP account (didn’t try IMAP) to use > STARTTLS (the default) against a server that does not support SSL, Would it be wrong to it difficult to find such a production server? Although one might be able to config/cripple one
Summary: High CPU usage attempting STARTTLS against a server that does not support it → High CPU usage attempting STARTTLS against a server that does not support it/SSL
You need to log in before you can comment on or make changes to this bug.