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

Issue metadata

Status: WontFix
Closed: Aug 2012
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug-Regression

  • Only users with EditIssue permission may comment.

Sign in to add a comment

Issue 141182: NBC tab starts using infinite memory

Reported by, Aug 7 2012 Project Member

Issue description

Google Chrome	22.0.1228.3 (Official Build 150281) dev
Platform	2722.0.0 (Official Build) dev-channel lumpy
WebKit	537.4 (@124674)
JavaScript	V8

What steps will reproduce the problem?
1. Login to
2. Navigate to
3. Go to full screen mode and switch to 1080p.
4. Wait for 10-15 minutes.
5. Check memory usage for NBC tab.

5.1 There seems to be a memory leak. The tab memory usage grows infinite. 

I think this is a regression. We didn't notice this issue last week.
Screenshot 2012-08-07 11:57:43 AM.png
305 KB View Download

Comment 1 by, Aug 7 2012


Comment 3 by, Aug 7 2012

Status: Assigned

Comment 4 by, Aug 7 2012

This is youtube flash player, correct? For me it is. Could you right-click on it to doublecheck? Were you able to repro this on any other youtube videos or just this specific site?

Comment 5 by, Aug 7 2012

Can we temporarily disable VA API if that fixes this leak? I don't want to block dev or any other channel on this feature for now.

Also seeing top crash from that stack - see, not sure if it is related.

Comment 6 by, Aug 7 2012

I don't think we should disable it -- your data is based on a build which doesn't have the fixes.

Comment 7 by, Aug 7 2012

Are we seeing this on other video streaming sites as well?

Comment 8 by, Aug 7 2012

Yes, this is Youtube Flash player.  This is specific to NBCOlympics site. Not reproducible on Youtube 1080p videos.

Will test with live streaming site and update this issue.

Comment 9 by, Aug 7 2012

Rohit: The reason it would be nice to find a repro on another streaming site is that NBColympics is particularly hard to debug. I assume it won't work under Linux or with the --no-sandbox flag.

Comment 10 by, Aug 7 2012

zel: this if Flash, so there should be no VA API running.

Comment 11 by, Aug 7 2012

I'm about to throw it under gdb, we'll see what's going on.

Comment 12 by, Aug 7 2012

Labels: Noteworthy

Comment 13 by, Aug 7 2012

So I don't see it leaking, at least not too much. Here is a before/after:

27149 root      20   0 1841m 241m  43m S  122  6.2   3:45.89 /usr/local/chrome/chrome --type=ppapi --channel=26902.4.195388842 --no-sandbox --lang=en-US
26922 root      20   0  496m 150m  72m S    7  3.9   0:36.35 /usr/local/chrome/chrome --type=gpu-process --channel=26902.0.37954832 --disable-gpu-sandbox --disable-gpu-watc
27046 root      20   0 1040m 121m  32m S    4  3.1   0:47.60 /usr/local/chrome/chrome --type=renderer --no-sandbox --lang=en-US --force-fieldtrials=ConnCountImpact/conn_cou
26902 root      20   0 1342m 110m  54m S    9  2.8   0:48.79 /usr/local/chrome/chrome --disable-gpu-watchdog --disable-gpu-sandbox --gpu-startup-dialog --user-data-dir=/tmp


27149 root      20   0 2054m 252m  43m S  111  6.5  19:12.96 /usr/local/chrome/chrome --type=ppapi --channel=26902.4.195388842 --no-sandbox --lang=en-US                    
26922 root      20   0  497m 151m  73m R   12  3.9   1:55.82 /usr/local/chrome/chrome --type=gpu-process --channel=26902.0.37954832 --disable-gpu-sandbox --disable-gpu-watc
27046 root      20   0 1052m 146m  33m R   15  3.8   2:16.32 /usr/local/chrome/chrome --type=renderer --no-sandbox --lang=en-US --force-fieldtrials=ConnCountImpact/conn_cou
26902 root      20   0 1358m 110m  54m S   12  2.8   2:28.14 /usr/local/chrome/chrome --disable-gpu-watchdog --disable-gpu-sandbox --gpu-startup-dialog --user-data-dir=/tmp

So in 16 minutes, flash goes from 241 to 252M. The renderer goes from 121 to 146. The GPU and UI processes are stable.

My task manager reports 119M for the tab process.

This is on flash I'll try next.

Comment 14 by, Aug 7 2012

I can't even log in with flash

Comment 15 by, Aug 7 2012

In any case:
- this is not going through the vaapi path at all,
- I can't observe any serious leak on flash

Comment 16 by, Aug 7 2012

Ok so Chrome 22.0.1222 with flash doesn't seem to leak either (but I'll keep running it for a bit). So far:

Chrome 22.0.1222, flash no leak
Chrome 22.0.1222, flash no leak

I'll make an image with latest everything next, we'll see.

Comment 17 by, Aug 7 2012

Labels: -ReleaseBlock-Dev ReleaseBlock-Beta
I tried 3 times and couldn't repro the climbing memory usage on my Lumpy,  so removing the dev blocker label. Since I was able to repro it twice today morning, moving it to beta.

I am seeing that NBC tab is using ~200 MB of memory right now.

Comment 18 by, Aug 9 2012

Status: WontFix
this does not repro anymore

Comment 19 by, Oct 13 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 20 by, Mar 9 2013

Project Member
Labels: -Type-Regression -Area-UI -Feature-Flash -Mstone-22 -Noteworthy Type-Bug-Regression Hotlist-Noteworthy Cr-UI Cr-Content-Plugins-Flash M-22

Comment 21 by, Mar 14 2013

Project Member
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Comment 22 by, Apr 6 2013

Project Member
Labels: Cr-Blink

Comment 23 by, Apr 6 2013

Project Member
Labels: -Cr-Content-Plugins-Flash Cr-Internals-Plugins-Flash

Sign in to add a comment