Find Memory-Heavy Chrome Tasks Before Ending a Process
By ON Lab · Sources checked November 6, 2026
Open Chrome’s menu → More tools → Task Manager and select Memory to sort its tasks by memory use. Google recommends looking for resource-heavy tasks you no longer need. Identify the task and save its work before using End Process: Google warns that unsaved work in that task will be lost.
Observe before changing anything
Our suggested first step is to write down the slow page or action, then inspect the task list. Record the task label and memory reading at the time you notice the problem. Google’s guidance specifically mentions looking for items labeled Background page.
A high entry tells you which task is using resources at that moment. This observation alone does not establish a memory leak, a defective extension, or the cause of every browser freeze. This guide does not set a universal number above which a task must be closed.
Decide whether you still need the task
Check the label against the page or app you are using. If it contains ongoing work, save that work before deciding to end it. If you cannot identify the task or establish what would be lost, keep the observation and leave it running.
For example, a video you no longer need and a form containing an unfinished response require different decisions. The first may be disposable; the second has work to preserve. Sorting the list does not make that decision for you.
End only a task you chose to stop
Google’s documented sequence is to select the unwanted task, then choose End Process. Our suggested follow-up check is to return to the original activity and record whether its responsiveness changed. If it did not, report that result rather than declaring the cause fixed.
Keep the next investigation specific
If the problem continues, retain the affected address, task label, observed memory reading and what happened after the action. This article does not establish a GPU fix, a cache-deletion remedy or a reason to reset the browser. Those changes require guidance matched to the remaining symptom.
Scope: Chrome Task Manager’s documented memory sorting and stopping of unwanted tasks. Observation and a one-task comparison are not proof of a permanent performance repair.