Closed
Bug 422360
Opened 16 years ago
Closed 16 years ago
don't statically link browser components with crt if using jemalloc
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ted, Assigned: ted)
Details
Attachments
(1 file)
4.10 KB,
patch
|
benjamin
:
review+
damons
:
approval1.9+
|
Details | Diff | Splinter Review |
We started statically linking the browser components to the CRT a while ago to work around stupid manifest issues. Now that we're building our own CRT with jemalloc, we could just link them to the CRT we're building when jemalloc is enabled. This way the browser components will get jemalloc love too.
Attachment #308832 -
Flags: review?(benjamin)
Updated•16 years ago
|
Assignee: nobody → ted.mielczarek
Version: unspecified → Trunk
Updated•16 years ago
|
Attachment #308832 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 1•16 years ago
|
||
Comment on attachment 308832 [details] [diff] [review] don't statically link browser components when jemalloc is enabled Might help perf or mem usage a little, I don't know, but it seems like the right thing to do.
Attachment #308832 -
Flags: approval1.9?
Comment 2•16 years ago
|
||
Comment on attachment 308832 [details] [diff] [review] don't statically link browser components when jemalloc is enabled a1.9+=damons
Attachment #308832 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 3•16 years ago
|
||
Checked in.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•