Due to inactivity chrome video playback stuck (mouse also for a second or two)

Bug #1805544 reported by Paco Raxim
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu version - 18.04.1
Gnome shell - 3.28.3

Although there is a lot of chromium bug related to video playback, my issues seem to be related to the power management. (AMD M260 Topaz, HD5500) - USB mouse.

I have disabled the diming / screen saver.

I have set up GPU usage on chrome dev version. (M70 is not able to use the linux GPU built in drivers)

I'm using usb tethering from Xperia as the wifi connection dies periodically and it seems to make chrome tab unresponsive, even if kept refreshing.

I have a feeling similar issues happening on full-screen video playback. So the root cause is the same.

Even if I set Xperia to wifi always on the ubuntu disconnecting from the device less frequently why I'm playing video in full-screen mode.

Some flickering issue happens on non-full screen mode, but less frequently, and it's stable for half hour after the restart, but suddenly goes like crazy.

I have tested lots of combinations, for example when mesa was not installed and my amd card was not even visible. (HD5500 does not have h264 hardware acceleration, amd m260 has, and on dev version it was really visible, that cpu usage was going down from 30% to under 10%)

Some video needs more juice like 60-70%, but it does not really matter. Sometimes is very stable, sometimes not.

The problem less frequently happens on firefox, even if the CPU is hitting 80% mark.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-08-07 (477 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Package: chromium-browser 72.0.3610.2-0ubuntu1~ppa4~18.04.1 [origin: LP-PPA-saiarcot895-chromium-dev]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Tags: bionic third-party-packages
ThirdParty: True
Uname: Linux 4.15.0-39-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-08-24 (95 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers video wireshark
_MarkForUpload: True
modified.conffile..etc.default.chromium-browser: [deleted]

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If your mouse is getting stuck also, then that wouldn't be a web browser bug. More likely a shell bug, maybe bug 1690719.

What kind of mouse are you using? USB? Wireless?

affects: xorg (Ubuntu) → chromium-browser (Ubuntu)
Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Paco Raxim (raxim1)
description: updated
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think the essence of this bug is the "stuck (mouse also for a second or two)".

So:

1. What Ubuntu version are you using?

2. What shell are you using?

3. Please run 'apport-collect 1805544' on the affected machine to send us more information about it.

Revision history for this message
Paco Raxim (raxim1) wrote : Dependencies.txt

apport information

description: updated
tags: added: apport-collected bionic third-party-packages
description: updated
Revision history for this message
Paco Raxim (raxim1) wrote : HookError_chromium_browser.txt

apport information

Revision history for this message
Paco Raxim (raxim1) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Paco Raxim (raxim1) wrote : ProcEnviron.txt

apport information

Revision history for this message
Paco Raxim (raxim1) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Paco Raxim (raxim1) wrote : RelatedPackagesPolicy.txt

apport information

Changed in chromium-browser (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. This now sounds like gnome-shell bug 1690719.

The issue with gnome-shell is that it's a single threaded process so anything holding up the event loop will delay both graphics output and even mouse movement.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.