The default bug view has changed. See this FAQ.

Don't build the jstracer by default

RESOLVED FIXED in mozilla10

Status

()

Core
JavaScript Engine
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: Matheus Kerschbaum, Assigned: Matheus Kerschbaum)

Tracking

Trunk
mozilla10
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
+++ This bug was initially created as a clone of Bug #693815 +++

Now that the tracer is disabled we should consider not building it by default, for a small win in binary/installer size.
Flags: in-testsuite-
(Assignee)

Comment 1

6 years ago
Created attachment 569907 [details] [diff] [review]
patch
Attachment #569907 - Flags: review?(khuey)
Comment on attachment 569907 [details] [diff] [review]
patch

This looks fine, but I'd rather one of the js people sign off on it.
Attachment #569907 - Flags: review?(khuey) → review?(dmandelin)
Attachment #569907 - Flags: review?(dmandelin) → review+
Matheus, can you measure the binary/installer size win?
I have a local patch that removes the tracer entirely, it was about ~500KB from the js binary on Linux.
I'd like browser-level measurements, before and after :)  I guess it's libxul that will end up smaller?
At least on Windows, libmozjs is still built separate from libxul.
(Assignee)

Updated

6 years ago
Keywords: checkin-needed
http://hg.mozilla.org/integration/mozilla-inbound/rev/8c0a324fc4ed
Keywords: checkin-needed
Target Milestone: --- → mozilla10
https://hg.mozilla.org/mozilla-central/rev/8c0a324fc4ed
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.