Closed Bug 1121162 Opened 5 years ago Closed 5 years ago

leakchecks become permaorange when async plugin init is turned on

Categories

(Core :: Plug-ins, defect)

x86
All
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla38
Tracking Status
firefox36 --- unaffected
firefox37 + fixed
firefox38 --- fixed

People

(Reporter: aklotz, Assigned: aklotz)

References

Details

Attachments

(1 file)

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.
Attachment #8555386 - Flags: review?(jmathies)
Assignee: nobody → aklotz
Status: NEW → ASSIGNED
Attachment #8555386 - Flags: review?(jmathies) → review+
https://hg.mozilla.org/mozilla-central/rev/fe0c7de37b32
Status: ASSIGNED → RESOLVED
Closed: 5 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.
Comment on attachment 8555386 [details] [diff] [review]
Resume stream listener before destroying it

Aurora+
Attachment #8555386 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.