Closed Bug 1666045 Opened 4 years ago Closed 4 years ago

Significant memory leak with Grammarly addon, browser becomes unresponsive.

Categories

(Core :: Privacy: Anti-Tracking, defect, P2)

Firefox 82
defect

Tracking

()

RESOLVED FIXED
83 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox80 --- unaffected
firefox81 --- disabled
firefox82 --- disabled
firefox83 --- fixed

People

(Reporter: kjacobs, Assigned: dimi)

References

(Regression)

Details

(Keywords: regression)

Attachments

(3 files)

Attached image x9tgjbk.png

Noticed in Nightly 82, the issue does not occur in 81.

STR:

  1. Load the Grammarly addon (you shouldn't need to sign up or sign in, just click activate).
  2. Open an MDN page in Edit mode and try to right-click a link and edit it.
  3. The pop-up takes a while to appear and memory usage climbs.

After a few seconds, the browser slows and becomes unresponsive. Reproduces on Mac and Windows. The attached screenshot was taken with a brand new profile.

Nightly profile: https://share.firefox.dev/2FIbMxV (can't run if for more than a few seconds, else the capture seems to time out and hang).
Beta profile: https://share.firefox.dev/3hJwrP2

Is there any chance you could run mozregression to see what broke this?

Flags: needinfo?(kjacobs.bugzilla)

mozregression points to https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=1e2a698cb1870ac8fc161f1e0c23111d071384c1, so I'm not sure why the problem doesn't show up in Beta (81 with Build ID 20200917005511).

However, in Nightly, if I turn tracking protection to "Custom" with all options unchecked and restart the browser, it works as expected (~700MB of memory used by Firefox). With tracking protection set to "Standard" or "Strict" the problem occurs (memory use quickly jumps to ~1.4GB and continues to grow).

Flags: needinfo?(kjacobs.bugzilla)
Component: General → Privacy: Anti-Tracking
Flags: needinfo?(dlee)
Product: Firefox → Core
Regressed by: 1652244
Severity: -- → S2
Priority: -- → P2
Assignee: nobody → dlee
Status: NEW → ASSIGNED
Flags: needinfo?(dlee)

Setting up the flags based on when Bug 1652244 was landed.

Has Regression Range: --- → yes

(In reply to Kevin Jacobs [:kjacobs] from comment #3)

so I'm not sure why the problem doesn't show up in Beta (81 with Build ID 20200917005511).

dFPI is Nightly-only (see the network.cookie.cookieBehavior pref).

we have found a solution for this bug, but it requires the patch in Bug 1663192

Depends on: 1663192
Pushed by dlee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a1031c6d4c03
Use principal to do the third-party check when the page is a about page r=timhuang
https://hg.mozilla.org/integration/autoland/rev/d16260bd4230
Test case to verify whether an about page in iframe has access to cookie r=timhuang
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: