Chromium-browser memory leak when showing video
922 views
Skip to first unread message
bergin
Dec 28, 2011, 3:55:37 AM12/28/11
to Chromium-dev
Hi,
When running Chromium 15.0.874.106 Ubuntu 11.10 on a web-page with
html5 video tags we experience a memory leak.
This behavior has been seen regardless of used video format (ogg,
webm, h264) and it has also been see in later version of the chromium-
browser (17.x).
During the test the memory increase is around 10MB/h. We have seen in
other tests that the if the browser is left running for a longer time,
it will consume all available memory, which in the end will crash the
system.
The following html-code is used to test and is run on a Apache server:
---------
<!DOCTYPE HTML>
<html lang="en">
<head>
<meta charset=utf-8>
<title>Video Player Test Page</title>
</head>
<body>
<div id="container" margin="0" padding="0" border="0">
<header>
<h1>Video Test Page</h1>
</header>
<section>
<hgroup>
<video src="video/sintel_trailer-720p.mp4" type='video/
mp4; codecs="avc1.42E01E, mp4a.40.2"' video width="1080" height="720"
margin="0" padding="0" border="0" loop="loop" autoplay></video>
</hgroup>
</section>
</div>
</body>
</html>
---------
Have anyone seen any similar behaviour? Are there any work-around to
avoid this increase in memory?
Regards,
/Peter
When running Chromium 15.0.874.106 Ubuntu 11.10 on a web-page with
html5 video tags we experience a memory leak.
This behavior has been seen regardless of used video format (ogg,
webm, h264) and it has also been see in later version of the chromium-
browser (17.x).
During the test the memory increase is around 10MB/h. We have seen in
other tests that the if the browser is left running for a longer time,
it will consume all available memory, which in the end will crash the
system.
The following html-code is used to test and is run on a Apache server:
---------
<!DOCTYPE HTML>
<html lang="en">
<head>
<meta charset=utf-8>
<title>Video Player Test Page</title>
</head>
<body>
<div id="container" margin="0" padding="0" border="0">
<header>
<h1>Video Test Page</h1>
</header>
<section>
<hgroup>
<video src="video/sintel_trailer-720p.mp4" type='video/
mp4; codecs="avc1.42E01E, mp4a.40.2"' video width="1080" height="720"
margin="0" padding="0" border="0" loop="loop" autoplay></video>
</hgroup>
</section>
</div>
</body>
</html>
---------
Have anyone seen any similar behaviour? Are there any work-around to
avoid this increase in memory?
Regards,
/Peter
PhistucK
Dec 28, 2011, 5:19:13 AM12/28/11
to peta...@gmail.com, Chromium-dev
Chrome 15 is no longer supported, it is the previous stable version, so, please, try again with Chrome 16 (and 17 beta) and if it still reproduces, search crbug.com for an existing issue and star it. If you cannot find one, file a new issue at new.crbug.com.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.
Thank you.
☆PhistucK
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Paweł Hajdan, Jr.
Jan 2, 2012, 10:38:32 AM1/2/12
to phis...@gmail.com, peta...@gmail.com, Chromium-dev
Even better, if you can use e.g. Valgrind to find out what is leaked and where, it's going to make fixing this even easier and faster.
Peter Bergin
Jan 4, 2012, 5:13:12 AM1/4/12
to Chromium-dev
I have now done the same test with "Chromium 18.0.989.0 Ubuntu 11.10" and the result is much better. Still leaking a bit but not that much. During 24h I have observed a leak for apprpoxiamtely 5-9MB. I will see if I can manage to to a more detailed study later on with Valgrind to track this down further. I will not report any bug in this right now.
Regards,
Paweł Hajdan, Jr.
Jan 4, 2012, 5:22:23 AM1/4/12
to peta...@gmail.com, Chromium-dev
You have a repro case that you say is reliable, so it's better to file a bug even for a small leak (and IMO it's not so small). When you have more details later that's of course great, but I don't recommend waiting until you have "perfect" info before filing the bug.
Timur Iskhodzhanov
Jan 25, 2012, 3:34:06 AM1/25/12
to peta...@gmail.com, Chromium-dev
Timur Iskhodzhanov
Jan 25, 2012, 3:36:23 AM1/25/12
to peta...@gmail.com, Chromium-dev
However please note that a growing memory usage is not always a "leak".
E.g. an infinite loop allocating objects and pushing the pointers into
a global vector is not a "leak" but indeed grows the process memory
usage.
Such errors are not easily detectable using Valgrind unfortunately.
Reply all
Reply to author
Forward
0 new messages