255433 - Firefox DLLs/EXEs not bound

Status: RESOLVED WONTFIX

(Firefox Build System :: General, enhancement)

Description

[Peter G. Toennies]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

The load time for Firefox can be improved if the EXEs/DLLs are bound. You can
see from various tools that Microsoft does this with Internet Explorer DLLs/EXEs
but Firefox does not. Some tools that are helpful to determine this are lipo32
and pedump.  You can download these from http://www.wheaty.net to determine
this.  If a DLL/EXE is not bound, the lipo32 tool will show this.  See
http://msdn.microsoft.com/msdnmag/issues/0500/hood/default.aspx for information
on why bind is important to performance.

Also, see http://staff.develop.com/igriffiths/techinfo/winmem.html and
http://www.msdnaa.net/content/?ID=1323

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/tools/bind.asp
for usage information on bind. As part of the install package for firefox
someone should do a bind.  Microsoft does this for many of their products such
as Microsoft Office.  This may help startup performance by about 6%.

Reproducible: Always
Steps to Reproduce:
1.  Download the lipo32 tool from http://www.wheaty.net.  The tool is in the
liposuction32 download.  Also, download pedump from the same site.
2.  open a command prompt
3.  change to the directory where firefox is installed, e.g. c:\program
files\mozilla firefox
4.  for /f "tokens=*" %i in ('dir /s /b *.dll *.exe') do lipo32 "%i"
Actual Results:  
The lipo32 tool will show that the EXEs/DLLs are not bound.  Also, you can run
pedump on the EXEs/DLLs and it will not show any bound import descriptors for
the files.

Expected Results:  
The install package should bind the DLLs/EXEs after they are installed.  It is
important to run bind on the user's machine since bind will link DLLs/EXEs to
system DLLs which will likely be different from the build machine and the target
machine.

Comment 1

[Peter G. Toennies]

I believe the Mozilla browser has the same problem.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

Not sure if this has been discussed before. Confirming, since I can't find a dupe.

Comment 3

[Kim Moir [:kmoir] ET]

triaging, closing old bug