If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Firefox 3.7(-?)] Build Optimized builds with --enable-logrefcnt

RESOLVED INVALID

Status

Release Engineering
General
--
major
RESOLVED INVALID
8 years ago
4 years ago

People

(Reporter: sgautherie, Unassigned)

Tracking

({regression})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
Example:
{
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1271031669.1271032176.17793.gz&fulltext=1
WINNT 5.2 mozilla-central opt test mochitests-2/5 on 2010/04/11 17:21:09

WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected!
}

These builds use the 'nightly' config, which, unlike the 'unittest' config, doesn't have this option :-/

Comment 1

8 years ago
IIRC, we're doing this intentionally.
Refcount logging should be on in debug builds, so we should have coverage for that particular changeset.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

8 years ago
I don't think Optimized and Debug builds are equivalent ... but I won't argue.
(In reply to comment #2)
> I don't think Optimized and Debug builds are equivalent ... but I won't argue.

Nevertheless, Aki is right that refcnt logging is purposely turned off in optimized builds. Refcnt logging affects performance, and is therefore undesired in opt builds, which are performance tested.
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.