Daily Build Thread 2010-10-13 Through 2010-10-19

[rsx11m]

test failures in Thunderbird, xpcshell tests on Mac OSX, and the mozmill tests don't run on either Mac or Windows.

Well, no burning tinderbox any more, but still failing tests. Mozmill is running again but fails on composition tests for obvious reasons.

[rsx11m]

#604493, Composition Window broken on trunk builds due to tracemonkey landing (merge of compartments) [all]

This has been "upgraded" to a MailNews Core bug, where composition in both SeaMonkey Mail & News and HTML Composer is broken as well. Thus, that check-in effectively killed the editor...

[Bozz]

#604493, Composition Window broken on trunk builds due to tracemonkey landing (merge of compartments) [all]

This has been "upgraded" to a MailNews Core bug, where composition in both SeaMonkey Mail & News and HTML Composer is broken as well. Thus, that check-in effectively killed the editor...

Looks like it happened before compartments.

Comment 12

I've just double-checked, the editor stuff was broken before the compartments landing, so the warnings there aren't anything to do with this specific bug.

[Bozz]

If anyone is interested in showing only the display name from your address book in the threadpane, I just installed Unified Display Names 0.1. You can narrow down the From and Recipient columns a good bit to give more room for the Subject to display. Nice.

[Nomis101]

Since I've downgraded from the broken build to the 13. Okt build, TB also takes 5-10 seconds to start. This is reproducible. I can close it, open again, close... Everytime it takes 5-10 seconds to start.

[Bozz]

Yep...it's been slow for me for some time now but I've noted that before. Don't know what could be causing it.

[Nomis101]

Yep...it's been slow for me for some time now but I've noted that before. Don't know what could be causing it.

OK, because I've now heard several reports from this, I've opend Bug 604788.

[Bozz]

^^Thanks. Hopefully they will look into it and find something that's causing the slow start up.

[JoeS]

I'm really not seeing any substantial change in startup time here.
(Note that I am working on an oldish comp here, so have never seen a startup time of less than 5 sec.)

Here's what I did to evaluate using the same profile with 3.3 compared to 3.1
First load after bootup in Win2k
3.1=about 12 sec
3.3=about 14 sec

Subsequent restarts:
3.1=5 sec
3.3=6-7 sec

So, the impact here is negligible.

One thing that has always affected startup time for me is the number of folders in the folderpane (I have many)
And if the Newsgroups are expanded or not.(unexpanded is much faster)

You might try a test profile with a minimum configuration, to see what that does.

[Hanki]

sometimes it may startup on my PC about 5secs ( first startup ) but its different at times, it randomly chooses how long it will take to startup on first start

[Nomis101]

One thing that has always affected startup time for me is the number of folders in the folderpane (I have many)

I have only one folder, with 10 emails. So this should't harm.

You might try a test profile with a minimum configuration, to see what that does.

I've tried that, I've also tried starting in safe-mode. It still now takes 5-10 seconds. Normally it only takes 0.75-2 seconds to start. I will see what will happen if I update to a newer version.

[rsx11m]

Looks like Neil is up to a solution for #604493, keeping fingers crossed!

[Nomis101]

Looks like Neil is up to a solution for #604493, keeping fingers crossed!

The attached patch from Neil works for me and fix the issue. But I don't know how long it will take to get this in, because it is an m-c patch and you need approval (and review) for it.

[rsx11m]

Neil is a peer for editor, thus he could review that patch, the only problem being that he wrote it himself.

Let's see how quickly Blake Kaplan (usually doing HTML-parser and JavaScript stuff according to the list) gets to it. At least, the patch apparently can be checked in with the remaining issues deferred to follow-up bugs, thus hopefully not blocking trunk any more after that.

[iTIE]

Breaking the compose window is one heck of an "whooops, m'bad."

Oh well, it'll get some attention since it's kind of hindering about half of the functionality of an email client. Gotta expect these things if we're using nightly builds.