Closed
Bug 169003
Opened 22 years ago
Closed 22 years ago
merge mozbrwsr into appcomps
Categories
(SeaMonkey :: UI Design, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.2beta
People
(Reporter: alecf, Assigned: alecf)
References
Details
(Whiteboard: fix in hand)
Attachments
(2 files)
20.34 KB,
patch
|
bryner
:
review+
jag+mozilla
:
superreview+
|
Details | Diff | Splinter Review |
6.87 KB,
patch
|
bryner
:
review+
jag+mozilla
:
superreview+
|
Details | Diff | Splinter Review |
The mozbrwsr dll is only 16k, and history has shown that DLL overhead is somewhere around 12k on disk (and 30k in memory) so I'm merging it into appcomps in an effort to reduce bloat. My guess is that appcomps will get about 4k bigger... since this DLL goes away, thats both a 12k win, and one less DLL to load at startup. patch forthcoming.
Assignee | ||
Comment 1•22 years ago
|
||
Here's the patch. the one thing I had to do was move the nsBrowserStatusHandler class declaration into the header file, so that the module could get at the constructor for the class. Can I get an r=blake, sr=jag?
Assignee | ||
Updated•22 years ago
|
Blocks: 163737
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: fix in hand
Target Milestone: --- → mozilla1.2beta
Comment 2•22 years ago
|
||
So what's the gain?
Comment 3•22 years ago
|
||
I was a bit too quick with the submit button there. I wanted it to read: So what's the measured gain?
Assignee | ||
Comment 4•22 years ago
|
||
I haven't checked DLL size on a release build yet, I'll post when I do. (But can I still get a review? There's no reason this should be in its own dll)
Assignee | ||
Comment 5•22 years ago
|
||
ok, I threw this onto a release build that was a few days old, here were the results: before: 32 components\mozbrwsr.dll 284 components\appcomps.dll 316 total after: 292 components\appcomps.dll so we see that appcomps.dll went up by 8k, and the total size went down by 24k. One thing I don't QUITE get is that on my nightly install from yesterday (where I got the number from comment 0) mozbrwsr is 16k, and appcomps is 271k... I'm not quite sure what the difference is, between my release build and the nightly build, but in any case we're of course seeing a net gain of at least 8k, probably 12k, and since there is a fixed cost runtime overhead of about 30k per dll, this is a great gain for us.
Comment 6•22 years ago
|
||
Comment on attachment 99394 [details] [diff] [review] merge mozbrwsr into appcomps Cool. Could it be that your one build is running with symbols (MOZ_PROFILE)? sr=jag
Attachment #99394 -
Flags: superreview+
Assignee | ||
Comment 7•22 years ago
|
||
this is just the mac project changes required to make this build
Comment 8•22 years ago
|
||
Comment on attachment 99455 [details] [diff] [review] the mac project changes sr=jag
Attachment #99455 -
Flags: superreview+
Updated•22 years ago
|
Attachment #99394 -
Flags: review+
Comment 9•22 years ago
|
||
Comment on attachment 99394 [details] [diff] [review] merge mozbrwsr into appcomps r=bryner
Comment 10•22 years ago
|
||
Comment on attachment 99455 [details] [diff] [review] the mac project changes r=bryner
Attachment #99455 -
Flags: review+
Comment 11•22 years ago
|
||
shouldn't this be marked fixed now? (was checked in 09/19/2002 12:00 by alecf%netscape.com)
Assignee | ||
Comment 12•22 years ago
|
||
geez give me a few minutes already.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•