Closed Bug 968536 Opened 11 years ago Closed 11 years ago

Remove ContentParent's phone-state-changed observer

Categories

(Core :: IPC, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla30
blocking-b2g 1.3+
Tracking Status
firefox28 --- wontfix
firefox29 --- wontfix
firefox30 --- fixed
b2g-v1.1hd --- unaffected
b2g-v1.2 --- wontfix
b2g-v1.3 --- fixed
b2g-v1.3T --- fixed
b2g-v1.4 --- fixed

People

(Reporter: khuey, Assigned: khuey)

References

Details

(Keywords: memory-leak)

Attachments

(1 file)

Attached patch PatchSplinter Review
I should have caught this in review :( This means we leak every ContentParent ever. It affects 1.2 too.
Attachment #8371123 - Flags: review?(n.nethercote)
Comment on attachment 8371123 [details] [diff] [review] Patch Review of attachment 8371123 [details] [diff] [review]: ----------------------------------------------------------------- r=me, but even better would be if you create an array of observer topic strings, and change ContentParent::Init() and ContentParent::ActorDestroy() to iterate over them. That would make it impossible for the additions and removals to not match.
Attachment #8371123 - Flags: review?(n.nethercote) → review+
That's a great idea. Let's do that in a followup so that we don't need to land churn on 1.3.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
I verified this is fixed. See bug 963290 comment 24.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: