New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 791465 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Memory overhead, phantom tabs

Reported by pavel.as...@gmail.com, Dec 4 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Using Chromium in casual mode
2. Opening several tabs
3. Observing extensive memory overhead that wasn't observed earlier.
4. When I check Win10 Task Manager, I notice Chrome shows that 10+ tabs are opened, whilst in reality it's only seven (7) of them.

What is the expected behavior?
Normal efficient memory management

What went wrong?
Excessive memory consumption

Did this work before? Yes 59

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0
 
Sketch33.png
159 KB View Download
Labels: Needs-Bisect

Comment 2 by woxxom@gmail.com, Dec 4 2017

Check in Chrome's built-in task manager - those additional processes are likely the browser extensions you have.
Cc: sc00335...@techmahindra.com
Labels: Triaged-ET Performance-Memory Needs-Feedback Needs-Triage-M62
Unable to reproduce this issue on reported version 62.0.3202.94 chromium using windows 10 with steps mentioned below.

1. Launched chromium and opened almost 20 tabs.
2. Opened Windows task manager and observed only one chromium task
3. Opened Chrome task manager and observed no high CPU usage.

@Reporter:Could you please retry the scenario by removing all extensions.
If the issue stills persist, it would be great if you could provide chrome://gpu details and a "memory-infra" trace.
When the system gets in this state: Follow below steps 1) Navigate to about:tracing 2) hit "record" in the upper left 3) select ""manually select settings"" 4) Make sure all checkmarks are clear other than "memory-infra" in the right column 5) hit record and allow the trace to run for ~30s before stopping it. 6) save the trace (upper left-hand corner) and attach here

Thanks!
Issue 791465.PNG
3.6 MB View Download
>> Check in Chrome's built-in task manager - those additional processes are likely the browser extensions you have.

Okay, probably you are right, and probably these are extensions, but! But number of processes in Task Manager is not squared against number of tabs.
I snapshoted/screenshoted a certain time moment, when There were opened 17 tabs, 2 incognito tabs, and the total number of my extensions is nine.
Anyway 17 + 2 + 9 is not 32 (what we see in task manager).

Again, what consumption indicators can be treated as normal? 

Does number that are highlighted on my screenshoted are "normal"? GPU load seems excessive, as only text pages are opened without any flash animation or smth like this.
Untitled.png
270 KB View Download
Sketch34.png
98.9 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Dec 5 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by woxxom@gmail.com, Dec 5 2017

Reporter, the built-in task manager in Chrome can be invoked from the browser menu or via Shift-Esc. It'll show all processes *actually* used by the browser, including GPU, extensions, plugins, tabs. It's customizable. You can compare the output to the system task manager and see if all processes are accounted for. 
OK, now I see that report from built-in task manager is correlated with Windows one.
We see here, that we have 26 tabs plus 9 extensions and we have 35 tabs in Win Task Manager.

It is novelty for me, that Browser itself and GPU are separate processes.
However, excesivve memory usage is still an issue. Will observe the situation further.
tabs_builtin.png
291 KB View Download
Labels: Needs-Feedback
@Reporter: Could you please send the tracing details by following steps mentioned in comment#3. This would help in further triaging of the issue.

Thanks!
>> Could you please send the tracing details by following steps mentioned in comment#3. This would help in further triaging of the issue.

Okay, I removed all the extension and retried the scenario. I opened 20+ tabs and measured the load. It was significantly less than previously, because of the lack of extensions I assume. BUT! But the number of tabs doesn't agree with number of processes anyway. 

Number of extensions is ZERO in this example, I wanna highlight, and we have 26 processes anyway.
Sketch22.png
240 KB View Download
Adding the extensions to browser increases the load up to the sky, which is not normal.
Sketch4444.png
158 KB View Download
Project Member

Comment 11 by sheriffbot@chromium.org, Dec 8 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
chrome://gpu


gpu_12.08.2017.htm
157 KB View Download
Memory trace
trace_overhead.json.gz
7.6 MB Download
As per Comment#12 & 13, reporter has provided GPU and memory trace related files

@Dev, can anyone from the dev team have a look at this issue

Cc: viswatej...@techmahindra.com
Labels: -Needs-Bisect
Status: WontFix (was: Unconfirmed)
It is not an expectation to have a 1:1 correspondence between processes to tabs. Chrome will create different processes for different reasons. A selection of process types includes...
* The Browser Process
* gpu-process
* nacl-loader
* Renderer
* ppapi
* Utility
* Watcher
* and more.

Each process uses the same Chrome bootstrapper but may load different DLLs to get the job done.

The browser process shouldn't use more than a few hundred MB. If it's using a lot, that's a real bug.

A renderer's process usage is a function of the memory used by a website. A process consumes memory in an OS and the OS charges it to that process. When a website consumes memory, it's technically supposed to be charged to the website but it is charged to Chrome because the OS doesn't know about websites. It only knows about processes.

There is some work to reduce the number of active renderers running by discarding the tab. This is somewhat like (but not exactly like) terminating a process on the OS.

Hopefully this answers some questions about processes in Chrome.

Sign in to add a comment