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

Issue 812047 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Memory leak when using setInterval with a function that includes a jquery post

Reported by gdmastra...@gmail.com, Feb 14 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36

Steps to reproduce the problem:
This is the javascript function that causes the problem:

function getM() {

    $.post("/get", {

        id: "1",
        _token: "random_token"
    }, function(data) {

        setTimeout(getM, 5000);
    });
}

Run this code in a page on Chrome for Ubuntu

What is the expected behavior?
Running just fine without memory increasing so much (I've come to a tab using 10 gigs of ram)

What went wrong?
Running said code causes the browser to increase memory consumption by about 1 or 2 MB per second.

I am on Ubuntu 17.10 64 bit, this issue happens only on Chrome on my Ubuntu machine.

I've also tested the code on Windows 10 64 bit Chrome 64.0.3282.167 and on Firefox 58.0.2 (Ubuntu), none of these browsers have memory leaking problems like the one i'm reporting.

Did this work before? N/A 

Chrome version: 64.0.3282.140  Channel: stable
OS Version: 17.10
Flash Version:
 

Comment 1 by ajha@chromium.org, Feb 14 2018

Labels: Needs-Triage-M64
Cc: sindhu.chelamcherla@chromium.org
Components: Platform>DevTools>Memory
Labels: Triaged-ET Needs-Feedback
Unable to reproduce this issue on reported version 64.0.3282.140 using Ubuntu 17.10 with steps mentioned below. Attaching screenshot for reference.

1. Opened https://bugs.chromium.org/p/chromium/issues/detail?id=812047 and opened devtools.
2. In console pasted function getM() {

    $.post("/get", {

        id: "1",
        _token: "random_token"
    }, function(data) {

        setTimeout(getM, 5000);
    });
}
3. Didn't observe any high memory usage in Task Manager.

@Reporter: Could you please check the screenshot and let us know if we miss anything? Also please check the issue on new profile which do not have any apps/extensions. This would help in further triaging of the issue
812047.png
460 KB View Download
Apparently the bug "works" only on my profile

I tried uninstalling completely chrome and reinstalling it fresh, but nothing changes.

I also tried disabling all extensions and everything's the same.

The only way to solve this seems to be to use the guest or any other profile.

As a note, /get returns an empty PHP array if that makes any difference.
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 14 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sindhu.chelamcherla@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: vamshi.kommuri@chromium.org
Labels: Needs-Feedback
@Reporter: It is understood from your comment#3 that the issue is not seen in a new profile with no extensions/apps, Any third party extension/apps installed in your profile might be the reason for memory leakage. As the issue is not seen in a clean profile, it would be highly helpful if given a confirmation whether we can close this issue.

Thanks!

Comment 6 by alph@chromium.org, Mar 3 2018

Components: -UI -Platform>DevTools>Memory UI>Browser>Profiles
Project Member

Comment 7 by sheriffbot@chromium.org, Mar 19 2018

Cc: droger@chromium.org bsazonov@chromium.org tangltom@chromium.org msarda@chromium.org ew...@chromium.org sabineb@chromium.org jlebel@chromium.org
Status: WontFix (was: Unconfirmed)
--Chrome Identity automated triaging--

This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

Sign in to add a comment