Closed Bug 1649477 Opened 7 months ago Closed 6 months ago

Leak involving in-process JSProcessActors

Categories

(Core :: DOM: Content Processes, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla80
Fission Milestone M6a
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- unaffected
firefox78 --- unaffected
firefox79 --- wontfix
firefox80 --- fixed

People

(Reporter: nika, Assigned: nika)

References

(Regression)

Details

(Keywords: regression)

Attachments

(4 files)

As Neil was adding a new JSProcessActor, they encountered a semi-reliable memory leak with the new in-process JSProcessActors introduced in bug 1633379.

This leak will only occur after introducing a new JSProcessActor with registered observer notifications.

Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8959d02b840f
Part 1: Move JSActor related files into their own directory, r=kmag
https://hg.mozilla.org/integration/autoland/rev/5b217aa88289
Part 2: Unify JSActor manager logic, r=kmag
https://hg.mozilla.org/integration/autoland/rev/eca6e9dce450
Part 3: Handle ReceiveRawMessage generically, r=kmag
https://hg.mozilla.org/integration/autoland/rev/830aa93d2b0c
Part 4: Improve a couple of error messages, r=kmag

nika: Triaging as reo is this bug for fission only use case or for the non fission use case as well?

Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0ad359f8308b
Part 1: Move JSActor related files into their own directory, r=kmag
https://hg.mozilla.org/integration/autoland/rev/d3c935827ef7
Part 2: Unify JSActor manager logic, r=kmag
https://hg.mozilla.org/integration/autoland/rev/d7810f45f0cb
Part 3: Handle ReceiveRawMessage generically, r=kmag
https://hg.mozilla.org/integration/autoland/rev/5907260fa468
Part 4: Improve a couple of error messages, r=kmag
Flags: needinfo?(nika)

(In reply to Kim Moir [:kmoir] ET from comment #8)

nika: Triaging as reo is this bug for fission only use case or for the non fission use case as well?

This bug should have no impact right now, as there are no users of the leaky code, but it was discovered when we were trying to add a new user. It'll only impact newly written code.

Regressions: 1655624
You need to log in before you can comment on or make changes to this bug.