The default bug view has changed. See this FAQ.

Remove tools/leaky

RESOLVED FIXED in mozilla15

Status

()

Core
Build Config
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: glandium, Assigned: glandium)

Tracking

({dev-doc-needed})

Trunk
mozilla15
dev-doc-needed
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 619579 [details] [diff] [review]
Patch

Leaky isn't built by default, isn't built on any tinderbox build and doesn't support anything other than x86 (not even x86-64). I think it can safely go away.
Attachment #619579 - Flags: review?(dbaron)
(Assignee)

Updated

5 years ago
Assignee: nobody → mh+mozilla
Attachment #619579 - Flags: review?(dbaron) → review+
(Assignee)

Comment 1

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/aa8d5b3a2928
Target Milestone: --- → mozilla15
(Assignee)

Updated

5 years ago
Keywords: dev-doc-needed
https://hg.mozilla.org/mozilla-central/rev/aa8d5b3a2928
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
XPCOM_MEM_LEAKY_LOG still exists, and there's some code in xpcom/base/nsTraceRefcnt.cpp that relies on it -- search for |gLogToLeaky|. Can that code be removed?
Flags: needinfo?(mh+mozilla)
I believe it can.
(Assignee)

Comment 5

3 years ago
Cf. dbaron
Flags: needinfo?(mh+mozilla)
> XPCOM_MEM_LEAKY_LOG still exists, and there's some code in
> xpcom/base/nsTraceRefcnt.cpp that relies on it -- search for |gLogToLeaky|.

It's gone now.
You need to log in before you can comment on or make changes to this bug.