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

Issue 722127 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

I suspect Chrome has memory leak on a Seeking Alpha page

Reported by ianfarbr...@yahoo.com, May 14 2017

Issue description

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

Steps to reproduce the problem:
1. go to https://seekingalpha.com/article/4073026-weighing-week-ahead-investors-fear-another-watergate
2. observe memory usage in Windows and/or Chrome Task Manager

What is the expected behavior?
Memory will stay at a 'reasonable' level.

What went wrong?
Over time, memory can go from mid-200MB to over 1400MB !!!
A refresh of the page will reset the memory (takes a bit of time to go all the way back down).

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 25.0 r0

The Seeking Alpha article is a fairly long one that comes out as part of a series every Sunday. It invariably has many useful links to other articles, which I frequently go and read while going through the main article.

I've noticed this kind of odd memory behavior for a while now (at least several months). I don't think it used to be as bad. I have noticed similar behavior (I think) on *some* other Seeking Alpha pages, but definitely not all - but then most of the articles are not as long, and don't have as many links out.

Anyway, today I noticed that the pattern seemed to be reproducible, so decided to take some screenshots and report it. In the sequence of six captures of Chrome Task Manager, the first four show the memory progressively increasing. Then I did a refresh, and the last two show the memory decreasing. I included a capture of Windows Task Manager at stage 4 simply to give an idea of the overall state of the system memory. I included a list view of the captures in order to provide a record of the actual times of the various items.

P.S. I notice that there are MANY reports of potential memory leak issues, but since I had no way of figuring out which one(s) this might relate to decided it was better to submit it on its own, and let someone who knows what they are doing decide if it should be combined with any of the other ones.
 
Capture Chrome Task Manager 1.PNG
83.4 KB View Download
Capture Chrome Task Manager 2.PNG
75.8 KB View Download
Capture Chrome Task Manager 3.PNG
73.0 KB View Download
Capture Chrome Task Manager 4.PNG
75.9 KB View Download
Capture Windows Task Manager 4.PNG
38.9 KB View Download
Capture Chrome Task Manager 5.PNG
78.5 KB View Download
Capture Chrome Task Manager 6.PNG
72.7 KB View Download
Capture Folder view for snip times.PNG
65.5 KB View Download
P.S. I strongly suspect (although it is basically only a hunch) that it is the ads on the page that cause the leak.
Labels: Needs-Triage-M58
Cc: krajshree@chromium.org
Components: Internals>Core
Labels: Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome reported version #58.0.3029.110 and latest canary #60.0.3103.0.

Attached a screen cast and screenshot for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to https://seekingalpha.com/article/4073026-weighing-week-ahead-investors-fear-another-watergate
2. Observe that memory usage in windows and Chrome Task Manager. In chrome task manager it remained at a reasonable level i.e it did not cross 150 MB and fluctuated between 100 and 150 MB.

ianfarbrother@ - Could you please check this issue on latest canary #60.0.3103.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
722127.mp4
2.6 MB View Download
memory.JPG
102 KB View Download
Thanks for trying to reproduce this - however, the screencast only shows 48 seconds. If you look at the Capture Folder image that I uploaded to show the capture times in my initial post, you will notice that the capture times are around 10 mins or so, and the whole process of 'zooming up' took around 35 minutes.

So I think you need to wait that kind of time in order to tell whether it is reproducible or not.

Btw, today I noticed it on another of the weekly series I read, this one coming out on Saturdays: https://seekingalpha.com/article/4074958-s-and-p-500-weekly-update-new-high-s-and-p-media-circus-arrives-scene?v=1495302823&comments=show

It would be difficult for me to run a setup with Canary (I think). I only have one machine, which is my *production* machine, so I am very cautious about messing with it.

It did, however, occur to me that perhaps I'm not the only one having issues with some SA pages, so I am about to send an email to their tech support (tech-issues@seekingalpha.com) and/or whether it might be related to the specific ads I am getting. I am going to refer them to this thread and ask them to respond here if they can contribute anything to the discussion.

I also noticed (from the small left-corner pop-up that says things like 'Waiting for <page>') that they seem to have some kind of ad refresh loop that seems to trigger roughly every 10 seconds or so.

As far as apps and extensions are concerned, the only two I have loaded are Session Buddy (hard to see how that could affect anything), and Ad Block Plus (which is obviously relevant). However, Ad Block Plus is disabled for SA, so I doubt that it would cause this kind of problem.
Project Member

Comment 5 by sheriffbot@chromium.org, May 20 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@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
Well, I did a lot more experimenting this afternoon, while reading the latest installment of Jeff Miller's 'Weighing The Week Ahead' series. The short answer is that this now appears to be a problem with a *specific* ad on Seeking Alpha, rather than a Chrome problem. I will send this comment on to the SA tech people once I've finished writing it.

What prompted me to start this was that yesterday evening I started wondering whether the problem could be something in SA's javascript failing to release objects after using them. So I decided to check out Microsoft Edge. I also decided to see if I could induce the problem more easily on Chrome for reproducibility.

First, I found that the problem became more easily reproducible on Chrome simply by scrolling down the page - especially to the Comments section (and I noticed later, when I tried Edge, that this only shows up if you are logged in).

When I tried Edge - which was kind of a pain, although that was probably at least due in part to unfamiliarity with its controls - it initially appeared that I couldn't reproduce the problem. So, since the memory problem was such a nuisance on Chrome, I decided to go ahead and read it using Edge. It turned out that on a couple of the linked articles, I started seeing the problem, but still not on the main article, which seemed especially odd.

To cut a long story short, I eventually noticed that in the main article I wasn't seeing a particularly annoying ad from SRAX that only appears somewhat down the page (which is why scrolling is necessary in order to reproduce it), but then annoyingly follows you down the page as you continue reading. It also happens to update itself frequently, which I suspect is somehow at the root of the issue.

So, my best guess at this point is that there is no need for you to do any further work on this - at least until we get some kind of feedback from SA.

Thanks for your initial attempt to reproduce this ... Ian
Got a response from Seeking Alpha midweek to say that they have terminated the relationship with SRAX (yay!). Anyway, I've been monitoring things carefully since then, and have seen no sign of the problem recurring.

So you can go ahead and close this.

Thanks ... Ian

Comment 8 by hdodda@chromium.org, May 29 2017

Status: WontFix (was: Unconfirmed)
As per comment #7 , closing the issue . Please feel free to raise a new issue if you face any issues in latest chrome channels.

Thanks!

Sign in to add a comment