Chrome is OOM-killed when playing long Youtube videos on 512MiB Go device |
||
Issue descriptionThe problem: it's not possible to watch hour+ long Youtube videos on 512MiB Android Go devices because Chrome is OOM-killed after ~30 minutes. Examples (use google@ account): 1. https://docs.google.com/spreadsheets/d/1ONlD5qL0uT7WAXxd7jJBHcP3mpPEXs-4mmucFRii2NQ/edit#gid=0 (killed after 29 mins) 2. https://docs.google.com/spreadsheets/d/1NZUaGcz5ZI9KlUmwLTWEdjtVlrawCDRAPIOgRZ7qbzs/edit#gid=0 (killed after 40 mins) There are two components that consume large amounts of memory in the renderer process: (1) Media stack: ~34MiB with 30+1MiB demuxer limits ("Native Heap" in the sheets above) (2) XMLHttpRequest buffers allocated from PartitionAlloc ("Unknown" in the sheets above) Outside of the renderer, media.codec process consumes another ~30MiB of memory (depends on video quality). Right now playing Youtube pushes OS to the limit and Android frequently finds itself in critical memory situation (see "Event upgraded to critical" logcat messages in the sheets above). We need to reduce renderer memory footprint in order to avoid triggering critical memory situation at OS level.
,
May 30 2018
After fixes in issues 813909 and 831356 the situation got better, and now Chrome is able to play long videos. Android bug for media.codec is b/64852183.
,
May 30 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by dskiba@chromium.org
, Apr 10 2018