Potential memory leak with html5 videos (youtube, twitch.tv)
Reported by
nic.berb...@gmail.com,
Apr 4 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3060.0 Safari/537.36 Steps to reproduce the problem: 1. Start a video on youtube 2. Right-click > Loop 3. Open chromium's task manager 4. Memory keeps increasing until the tab crashes/gets discarded What is the expected behavior? The memory should be freed. What went wrong? The memory leaked until the tab was discarded (see flags below) Did this work before? N/A Chrome version: 59.0.3060.0 Channel: dev OS Version: 10.0 Flash Version: Version: Chromium 59.0.3060.0 (Official Build) (64-bit) Revision: c45b1c4ef18fa397013d1109dd9abe1f01543b3c-refs/heads/master@{#461321} Build: https://github.com/henrypp/chromium/releases/tag/v59.0.3060.0-r461321-win64 Build version: dev-codecs-nosync Last version: https://github.com/henrypp/chromium/releases/tag/v59.0.3053.0-r459656-win64 This bug could not be observed on youtube in the last version (see above), though it did exist for videos on Twitch.tv. The memory seems to get freed after pausing the video (see 4:50 in attached video) but not while it's looping. flags: --flag-switches-begin --allow-insecure-localhost --enable-appcontainer --enable-devtools-experiments --enable-es3-apis --enable-fast-unload --enable-grouped-history --enable-md-policy-page --enable-offline-auto-reload-visible-only --enable-site-settings --enable-tab-audio-muting --enable-lcd-text --disable-overlay-scrollbar --reduced-referrer-granularity --save-page-as-mhtml --secondary-ui-md --disable-smooth-scrolling --top-chrome-md=material-hybrid --enable-features=AutomaticTabDiscarding,CrossOriginMediaPlaybackRequiresUserGesture,MaterialDesignBookmarks,MaterialDesignExtensions,MaterialDesignHistory,NewAudioRenderingMixingStrategy,PostScriptPrinting,ViewsSimplifiedFullscreenUI,token-binding --disable-features=MaterialDesignSettings,ScrollAnchoring --flag-switches-end
,
Apr 4 2017
Update: The memory leak is now observed on soundcloud.com while listening to music on-repeat. Playing another music or reloading the page fixes the problem. I disabled the NewAudioRenderingMixingStrategy to test whether it had anything to do with the leak. It doesn't seem so. Link to the allocation profile, heap snapshot and allocation timeline: https://mega.nz/#F!NqJzBAzJ!4OAQIS_T0GUGImgNC7QGSw (I reloaded the page between the allocation profile and allocation timeline test)
,
Apr 6 2017
Unable to reproduce this issue on Windows 10 with chrome #59.0.3063.1 as per the steps and flags mentioned in the comment #0. Ran the 1 hr YouTube video continuously, didn't observe any crash. These are the flags status while launching chrome "--allow-insecure-localhost --enable-appcontainer --enable-devtools-experiments --enable-es3-apis --enable-fast-unload --enable-grouped-history --enable-md-policy-page --enable-offline-auto-reload-visible-only --enable-site-settings --enable-tab-audio-muting --enable-lcd-text --disable-overlay-scrollbar --reduced-referrer-granularity --save-page-as-mhtml --secondary-ui-md --enable-smooth-scrolling --top-chrome-md=material-hybrid --sync-url=https://chrome-sync.sandbox.google.com/chrome-sync/alpha --wallet-service-use-sandbox=1 --enable-features=AutomaticTabDiscarding,CrossOriginMediaPlaybackRequiresUserGesture,MaterialDesignExtensions,MaterialDesignHistory,NewAudioRenderingMixingStrategy,OmniboxEntitySuggestions,PostScriptPrinting,ViewsSimplifiedFullscreenUI,token-binding --disable-features=MaterialDesignSettings,ScrollAnchoring --flag-switches-end" nic.berbiche@ could you re-try the same scenario on clean profile with no apps & extensions and let us know your observations.
,
Apr 6 2017
,
Apr 6 2017
I was able to reproduce the memory-leak under a clean install of chrome #59.0.3060.0 following the same steps.
,
Apr 6 2017
Thank you for providing more feedback. Adding requester "kkaluri@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
,
Apr 9 2017
Updated to chrome #59.0.3067.0, the bug has disappeared and I am no longer able to reproduce it.
,
Apr 10 2017
@nic.berbiche -- Thank You for the update. Marking the issue as Won't Fix as per Comment#7. Please feel free to raise a new issue if the bug is again seen. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, Apr 4 2017