Closed
Bug 17032
Opened 26 years ago
Closed 14 years ago
Browser component DLLs should be combined
Categories
(SeaMonkey :: UI Design, defect, P1)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: sfraser_bugs, Assigned: jag+mozilla)
References
Details
(Keywords: perf, Whiteboard: [nav+perf])
In an effor to reduce the number of small DLLs, we need to combine the browser
component DLLs (which can usefully be combined) into a single larger DLL.
Summary: [Perf] Brower component DLLs should be combined → [DOGFOOD][Perf] Brower component DLLs should be combined
Comment 4•26 years ago
|
||
Keep Simon in the loop as this may conflict with his 5085 where he was talking
about *splitting* libraries (reconfiguring, actually) so less is loaded at
startup.
Summary: [DOGFOOD][Perf] Brower component DLLs should be combined → [Perf] Brower component DLLs should be combined
Whiteboard: [PDT-]
Target Milestone: M13 → M15
Keywords: perf
Summary: [Perf] Brower component DLLs should be combined → Broswer component DLLs should be combined
Updated•25 years ago
|
Target Milestone: M16 → Future
Reporter | ||
Comment 8•25 years ago
|
||
Judson, do we need to do this too? I still see the following small browser
component DLLS that could be combined:
AppShellDebug.shlb ?
FindComponentDebug.shlb
mozBrowserDebug.shlb
shistoryDebug.shlb
ucthDebug.shlb
webBrowserDebug.shlb
xferDebug.shlb
Comment 9•25 years ago
|
||
I consolodated those, on all platforms, which I was able to do (without diving
into law's specialized/complex APP_MODULE_MACRO thing). The list you show
contains those that weren't easily consolodated or should be left independent as
they are candidates for replacement by embedding parties.
Comment 11•25 years ago
|
||
nav triage team:
Would be very nice, but not critical for beta1. Marking nsbeta1-, more important
things to work on would be making xpcom startup faster
Updated•25 years ago
|
QA Contact: don → sairuh
Summary: Broswer component DLLs should be combined → Browser component DLLs should be combined
Comment 12•24 years ago
|
||
P1/Future? Strange combination. Any plans for this soon?
Keywords: mozilla0.9 → mozilla0.9.1
Comment 13•24 years ago
|
||
nav triage team:
Umm, won't the "static" build get us this?
Comment 14•24 years ago
|
||
Yes, but with the static build, we lose all the advantages of the component
system. We currently have lots of DLLs (about 90), and I'd bet this number could
be cut in half without too much pain.
Updated•24 years ago
|
Whiteboard: [nav+perf]
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
Comment 16•18 years ago
|
||
As of Firefox 3.0b2, only two DLLs are in the components directory: browserdirprovider.dll
brwsrcmp.dll
bsmedberg, stuart: Are these DLLs which could go into libxul or are they best off staying separate?
Assignee: law → jag
Status: ASSIGNED → NEW
QA Contact: bugzilla
Comment 17•18 years ago
|
||
Oh, and I'm assuming that Seamonkey will be in a similar position once libxul is enabled, yes?
Comment 18•18 years ago
|
||
They should not be in libxul: libxul is the platform by design, and Firefox is built on top of it. You could theoretically combine the two DLLs into one, but it won't affect performance noticably.
![]() |
||
Comment 19•14 years ago
|
||
WFM: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110212 Firefox/4.0b12pre SeaMonkey/2.1b3pre
Only suite.dll left
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•