[Bug 1698282] [NEW] Totem uses dramatically higher CPU than any other video player
Launchpad Bug Tracker
1698282 at bugs.launchpad.net
Thu Oct 5 08:36:46 UTC 2017
You have been subscribed to a public bug by Daniel van Vugt (vanvugt):
Totem uses dramatically higher CPU than any other video player.
Example 1: software playback under Gnome Shell Wayland:
totem: 120% (but drops to 80% in Unity7)
mplayer: 40%
vlc: 40%
[all are using ffmpeg for decoding]
Example 2: hardware-accelerated playback under Gnome Shell Xorg:
totem: 11%
gst-play-1.0: 3%
[both are using gstreamer-vaapi for decoding]
Since the decoding libraries are theoretically the same it sounds like
totem's performance problems might be in its rendering path.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libgstreamer1.0-0 1.12.0-2
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
Date: Fri Jun 16 12:57:11 2017
InstallationDate: Installed on 2017-05-03 (44 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: clutter-gtk
Importance: Medium
Status: Confirmed
** Affects: gstreamer1.0
Importance: Medium
Status: Fix Released
** Affects: clutter-1.0 (Ubuntu)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt)
Status: Confirmed
** Affects: clutter-gst-3.0 (Ubuntu)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt)
Status: Confirmed
** Affects: clutter-gtk (Ubuntu)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
** Affects: totem (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Released
** Tags: amd64 apport-bug artful performance
--
Totem uses dramatically higher CPU than any other video player
https://bugs.launchpad.net/bugs/1698282
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list