Closed Bug 1752635 Opened 4 years ago Closed 3 years ago

Investigate how processes and memory are being managed in Chromium

Categories

(GeckoView :: General, task, P2)

Unspecified
All
task

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: owlish, Assigned: kaya)

References

(Blocks 1 open bug)

Details

(Whiteboard: [geckoview:2022h2?])

It might be instructive to investigate how the priority of the processes is being Managed in Chromium and what are their conditions for tab reloads/unloads.

Severity: -- → S3
Priority: -- → P2
Whiteboard: [geckoview:2022h2?]
Assignee: nobody → kkaya

This investigation has been done and reported in several subtitles of the following document:
https://docs.google.com/document/d/1s9AqQ9Ixi-NzoitztuhEeP67-hvcUq7DHDZ6YbiWlS4/edit#

As seen from the document Fenix and Chrome comparison is also done. The document also mentions APIs that exist in Chrome but not in Fenix (such as ZygotePreloader) that cause a difference in the memory consumption of the content processes.

I think we can close this ticket.

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