leakchecks become permaorange when async plugin init is turned on

RESOLVED FIXED in Firefox 37

Status

()

Core
Plug-ins
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: aklotz, Assigned: aklotz)

Tracking

unspecified
mozilla38
x86
All
Points:
---

Firefox Tracking Flags

(firefox36 unaffected, firefox37+ fixed, firefox38 fixed)

Details

Attachments

(1 attachment)

Failures such as the one in bug 1064197 occur regularly in M1 and M3 (non-e10s) when running tests with Asynchronous Plugin Initialization turned on by default. This is actually pretty bizarre given that those leaked objects are not plugin-related.
Created attachment 8555386 [details] [diff] [review]
Resume stream listener before destroying it
Attachment #8555386 - Flags: review?(jmathies)
Assignee: nobody → aklotz
Status: NEW → ASSIGNED

Updated

3 years ago
Attachment #8555386 - Flags: review?(jmathies) → review+
https://treeherder.mozilla.org/#/jobs?repo=try&revision=063f36034ae1
https://hg.mozilla.org/integration/mozilla-inbound/rev/fe0c7de37b32
https://hg.mozilla.org/mozilla-central/rev/fe0c7de37b32
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Comment on attachment 8555386 [details] [diff] [review]
Resume stream listener before destroying it

Approval Request Comment
[Feature/regressing bug #]: async plugin init
[User impact if declined]: Will not have the option to ship asyncInit in 37
[Describe test coverage new/current, TreeHerder]: On m-c and locally. Tests that previously leaked with asyncInit turned on now pass.
[Risks and why]: None, trivial fix
[String/UUID change made/needed]: None
Attachment #8555386 - Flags: approval-mozilla-aurora?
Tracking as this impacts shipping asyncInit.
status-firefox36: --- → unaffected
status-firefox37: --- → affected
status-firefox38: --- → fixed
tracking-firefox37: --- → +
Comment on attachment 8555386 [details] [diff] [review]
Resume stream listener before destroying it

Aurora+
Attachment #8555386 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
https://hg.mozilla.org/releases/mozilla-aurora/rev/c785bf627bac
status-firefox37: affected → fixed
You need to log in before you can comment on or make changes to this bug.