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

Issue 886569 link

Starred by 1 user
Status: WontFix
Owner:
l...@chromium.org
Closed: Dec 14
Cc:
█ scut...@gmail.com
dgozman@chromium.org
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: web page can flood Console with logs and consume too much memory and cpu

Reported by scut...@gmail.com, Sep 19 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Steps to reproduce the problem:
1. use the chrome browser to make a request for the home page of the acer: https://www.acer.com.cn/index.html;
2. open the chrome devtools;
3. click the '注册'(which means sign up) button on the web page;
4. open the task manager of chrome;
5. just wait about 10 minutes patiently,during this time you can have a cup of tea, enjoy some pleasent music, etc;
6. now you will see the chrome browser almost run out the memory and it occupied too much cpu resource, just like the figure shown in the attached file.

What is the expected behavior?
the chrome browser should not eat all the memory space!!!We just visit a web page, and my computer is almost out of control!!!

What went wrong?
(1)This problem probably implys that the latest version of chrome browser have the memory leak bug when handling the AJAX request;
(2)Although the problem is like the issue:52411(fixed) in some way, it is likely that someone ever steps in the same river twice.

Did this work before? No 

Chrome version: 69.0.3497.100  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Hope my submission can help.
fingure1_occupation_of_memory_and_cpu.png
50.6 KB View Download
screenshot_sys_task_manager.png
59.2 KB View Download
screenshot_sys_task_manager_after_killing_chrome_exceptional_process.png
3.3 KB View Download

Comment 1 by susan.boorgula@chromium.org, Sep 19

Labels: Needs-Triage-M69

Comment 2 by krajshree@chromium.org, Sep 28

Components: Internals>Network

Comment 3 by mef@chromium.org, Oct 2

Components: -Internals>Network Platform>DevTools>Memory

Comment 4 by dgozman@chromium.org, Oct 8

Labels: Needs-Feedback
I cannot reproduce this one. Clicking on the '注册' button does issue a single network request, but nothing else happens. Could you please double check on your end?

Comment 5 by scut...@gmail.com, Oct 9 

But I still have reproduced this bug twice today...
The screenshots in the attached file are good evidence.
new_screenshot.rar
177 KB Download
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 9

Cc: dgozman@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 7 by phanindra.mandapaka@chromium.org, Oct 12

Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
 scutjyj@ Thanks for the issue...

Tried to reproduce the issue on reported chrome version 69.0.3497.100 using Windows 7.Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome 
2. Navigated the URL "https://www.acer.com.cn/index.html;"
3. Opened Dev tools >Clicked on '注册' observed register page popup and opened task manager and left it and came back after 10 min
As we are observed that cpu usage 0 and chrome browser usage high as per screencast

@Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end and Request you to retry this issue with fresh profile without any extensions  & apps or reset all the flags and let us know if issue still persists.

Thanks..!
886569.mp4
2.1 MB View Download

Comment 8 by hhli@chromium.org, Oct 15

Cc: scut...@gmail.com
Kindly CC the reporter

Comment 9 by scut...@gmail.com, Oct 22 

Sorry for replying so late.

I have tried again just now with all extensions closed and get the same result as before...
The extensions installed to my chrome browser is shown in the attached file.Also the screenshot of the result is included.

More details about my operation:

Besides opening the dev_tools and chrome task manager, I scroll the navbar of this web page several times randomly during 10 minutes.

Hope my work can help.
screenshot_extensions_20181022.png
53.5 KB View Download
screenshot_resources_20181022.png
54.7 KB View Download
screenshot_webpage_20181022.png
265 KB View Download
Project Member

Comment 10 by sheriffbot@chromium.org, Oct 22

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 11 by l...@chromium.org, Oct 31

Owner: l...@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: DevTools: web page can flood Console with logs and consume too much memory and cpu (was: web page using AJAX request cause chrome occupy too much memory and cpu resource)
Thanks for the report.  I had trouble reproducing this, but I was able to once or twice.  I'm not familiar with the page's JS, but it has a `onSlideChangeStart` function that calls `console.log` on a regular interval, in the repro scenario.

In my reproduction, the # of logs grew exponentially, and DevTools consumed more memory/CPU because it holds on to all messages until the Console is cleared.

Screenshot: https://imgur.com/a/A08X8O1

To better handle these cases, I'll explore ways for Console to monitor its own memory consumption.

Comment 12 by l...@chromium.org, Dec 14

Status: WontFix (was: Assigned)
After looking at heap snapshot differences, there seems to be no significant gain if the frontend dropped all console messages.  Simply receiving a flood of protocol messages can cause DevTools to spike in CPU / memory.  Since other efforts are addressing the memory consumption of DevTools holding onto protocol messages, I will close this.
►

Sign in to add a comment