Closed Bug 1015120 Opened 10 years ago Closed 9 years ago

Very slow starting of Thunderbird when font in autoconfig.js is predefined

Categories

(Thunderbird :: Untriaged, defect)

24 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tg, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20131021230807

Steps to reproduce:

We predefind font configuration in autoconfig.js like:

lockPref("msgcompose.font_face", "Calibri, Arial, Helvetica, Geneva, Swiss, SunSans-Regular");
lockPref("msgcompose.font_size", "medium");
lockPref("font.default", "Calibri, Arial, Helvetica, Geneva, Swiss, SunSans-Regular");
lockPref("font.default.x-unicode", "Calibri, Arial, Helvetica, Geneva, Swiss, SunSans-Regular");
lockPref("font.default.x-western", "Calibri, Arial, Helvetica, Geneva, Swiss, SunSans-Regular");




Actual results:

In this configuration startup of Thunderbird is > 30 secs. If we define a single font instead of a font-family the sympton is the same.

The sympton appears with Thunderbird Version 24.1.0 and higher on Windows XP, Windows 7 and Windows 8.1


Expected results:

Setting of fonts in autoconfig.js should not slow down the startup.
(In reply to tg from comment #0)
> In this configuration startup of Thunderbird is > 30 secs. 

just to be clear, 
a) how many seconds do you get without specifying font?
b) did it not happen with TB17?
Flags: needinfo?(tg)
Keywords: perf
tg?

(In reply to Wayne Mery (:wsmwk) from comment #1)
> (In reply to tg from comment #0)
> > In this configuration startup of Thunderbird is > 30 secs. 
> 
> just to be clear, 
> a) how many seconds do you get without specifying font?
> b) did it not happen with TB17?
Whiteboard: [closeme 2015-03-15]
Can't reproduce, closing
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(tg)
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2015-03-15]
You need to log in before you can comment on or make changes to this bug.