Closed Bug 1623557 Opened 5 years ago Closed 2 years ago

Navigating to a memory heavy page, and then navigating back does not release memory

Categories

(Core :: Graphics: WebRender, defect, P3)

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox78 --- wontfix

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

memory-report.json.gz
(deleted), application/x-gzip
Details
about:support
(deleted), text/plain
Details
Attached file memory-report.json.gz (deleted) —
  1. Go to the bugzilla page: https://bugzilla.mozilla.org/show_bug.cgi?id=1623548
  2. Click on the codepen.io link , to open the url in the same tab
  3. Watch memory grow. Should stabilize around 4GB or so.
  4. Click on the back navigation arrow on the address bar to navigate back to the original bugzilla page.
  5. Open task manger to confirm that the memory has not been released.

Additional step : Opening about:memory, and clicking on "minimize memory" wont work.

Attached file about:support (deleted) —
This happens on both WR/non-WR . Tried in my regular profile, as well as a new profile. Attaching about:support of my regular profile.

dupe comment

Priority: -- → P3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

This is likely to be "fixed" by fission. However navigating between such pages within the same site (and therefore the same process) will still be a problem. So I want to track it for memshrink-content anyway.

No longer blocks: wr-perf

memory doesnt increase on the testcase anymore

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: