Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

YouTube is failing to download poster images for videos

Description

Copied from https://lf-automotivelinux.atlassian.net/browse/SPEC-1870:

Regarding the first issue, YouTube is failing to download poster images for videos. 

YouTube is a heavy application for network and it sends a lot of request(> 35)t to a remote server for various resources. YouTube App was taking a long time to receive a response from the server.

> Enable remote debugging using chrome dev tool :

mkdir -p /var/luna/preferences cd /var/luna/preferences touch devmode_enabled touch debug_system_apps

then on your desktop browser connect to

<board_ip>:9998

After increasing the number of a tinyproxy process instance(to 10) in tinyproxy.confyoutube app started loading video smoothly. MaxClients = 10, MinSpareServers = 5, MaxSpareServers = 20, StartServers = 10

On EEL, it was working fine with existing setting MaxClients = 1,  StartServers = 1. That is a reason, changes for YouTube app are not merged in the wam-tinyproxy repository. Moreover, it doesn't make sense to a created unnecessary lot of tinyproxy for simple applications.

This task needs to be revisited and analyzed further.

Environment

None

Activity

Walt Miner 
February 11, 2019 at 11:11 PM

Close for FF 6.0.4 and GG 7.0.0

Lorenzo 
January 8, 2019 at 3:06 PM

Fixed on current flounder.chromium68 branch.

Henrique Ferreiro 
November 13, 2018 at 11:58 AM
(edited)

Setting MaxClients to 1 serializes all connections from web apps, making YouTube unusable. We need to further check why this was working on eel. Also, if having so many tinyproxy processes running is an issue, we should enhance tinyproxy to handle requests using threads.

For the time being, I'm proposing to revert the settings patch in https://github.com/Igalia/wam-tinyproxy/pull/4.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Priority

Created November 13, 2018 at 10:33 AM
Updated February 11, 2019 at 11:11 PM
Resolved January 8, 2019 at 3:06 PM

Flag notifications