Bug 8406 - xvmc eats cpu usage 100% and Fullscreen <-> Window make player black on AIGLX
Summary: xvmc eats cpu usage 100% and Fullscreen <-> Window make player black on AIGLX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (proprietary) (show other bugs)
Version: 7.1 (2006.05)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Andy Ritger
QA Contact: Xorg Project Team
Depends on:
Reported: 2006-09-23 07:36 UTC by sangu
Modified: 2018-06-12 19:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

nvidia-bug-report file (103.03 KB, text/plain)
2006-09-23 07:37 UTC, sangu
no flags Details

Description sangu 2006-09-23 07:36:23 UTC
xvmc eats cpu usage 100% and Fullscreen <-> Window make a player black  on AIGLX.

$mplayer -vo xvmc -vc ffmpeg12mc DVD or HDTV

nvidia driver 1.0.9625
OS :  Fedora development (20060923)
Comment 1 sangu 2006-09-23 07:37:01 UTC
Created attachment 7142 [details]
nvidia-bug-report file
Comment 2 José JORGE 2006-10-08 14:04:41 UTC
on which hardware, with which driver?
Comment 3 Daniel Stone 2007-02-27 01:33:40 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 4 James Jones 2007-04-23 16:02:28 UTC
Sangu, can you check if this still reproduces with the 100.14.03 beta drives or the 1.0-9755 drivers?  CPU usage was lowered in certain cases with XvMC/Xv in those drivers.
Comment 5 sangu 2007-04-24 23:45:33 UTC
The same problems happen in the 100.14.03 beta drives and the 1.0-9755 drivers.
In compiz(Gl composite windowmanager).
Using XvMC, mplayer has high cpu usage and flickering box.


OS :Fedora Rawhide (20070424)
VGA : NVidia 6800GS
CPU :  AMD X2 3800+
Mem :  2GB
Comment 6 Adam Jackson 2018-06-12 19:09:45 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.