Open Bug 1549936 Opened 5 years ago Updated 1 year ago

Investigate why the controller must cancelQuery to avoid leaks in Private browsing tests

Categories

(Firefox :: Address Bar, defect, P3)

Product:
Firefox
Component:
Address Bar
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox68 --- affected

People

(Reporter: mak, Unassigned)

References

(Blocks 1 open bug)

Details

In bug 1548817 I hit memory leak reports in private browsing tests, unless I explicitly invoked this.manager.cancelQuery(). We should investigate the underlying reason for those.

Severity: normal → S3
See Also: → 1696022

Just as a follow up from our recent bug scrub: To test whether this line of code is still required to prevent memory leak reports, I removed it and ran some tests on TreeHerder and it did seem to result in test breakages. Unsure if it was precisely the same as what occurred years ago, but the errors mention leaked windows.

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