don't statically link browser components with crt if using jemalloc

RESOLVED FIXED

Status

()

RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: ted, Assigned: ted)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 308832 [details] [diff] [review]
don't statically link browser components when jemalloc is enabled

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)
Assignee: nobody → ted.mielczarek
Version: unspecified → Trunk

Updated

11 years ago
Attachment #308832 - Flags: review?(benjamin) → review+
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 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+
Checked in.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.