Opened 15 years ago
Closed 14 years ago
Last modified 14 years ago
#6980 closed defect (invalid)
VLD XvMC broken in trunk on CLE266
| Reported by: | Owned by: | Janne Grunau | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - Video Playback | Version: | head |
| Severity: | medium | Keywords: | vld xvmc cle266 |
| Cc: | Ticket locked: | yes |
Description
I installed mythbuntu 9.04, enabled the weekly trunk builds and upgraded everything, so now I'm running mythtv from a recent version of trunk.
VLD XvMC runs at > 80% CPU (this was 45% CPU on mythtv-0.20).
Xine still runs smoothy at 30% CPU on the same content ruling out problems with the openchrome driver.
I'm running a VIA EPIA M1000 with CLE266.
Ronald Pijnacker
Attachments (2)
Change History (7)
Changed 15 years ago by
| Attachment: | mythfrontend.log added |
|---|
comment:1 follow-up: 2 Changed 14 years ago by
This appears to be a bug in the OpenChrome? driver related to surface creation. See http://www.gossamer-threads.com/lists/mythtv/users/418072#418072 and http://www.gossamer-threads.com/lists/mythtv/users/418145#418145 .
comment:2 Changed 14 years ago by
Replying to mdean:
This appears to be a bug in the OpenChrome? driver related to surface creation. See http://www.gossamer-threads.com/lists/mythtv/users/418072#418072 and http://www.gossamer-threads.com/lists/mythtv/users/418145#418145 .
No, the message about the not being able to create surfaces is merely a warning (albeit one that set a number of people, including myself on the wrong foot). The CPU usage is caused by how mythtv uses openchrome, since xine has no problems.
comment:3 follow-up: 4 Changed 14 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This is a driver problem, the driver needs to stop handing out surfaces when it runs low on memory.
comment:4 Changed 14 years ago by
Replying to danielk:
This is a driver problem, the driver needs to stop handing out surfaces when it runs low on memory.
As you can read in my previous comment, the fact that the driver is reporting that it cannot allocate surfaces anymore is just a warning. In fact: it is actually mythtv that keeps allocating surfaces until it can't (which is the real cause of this warning).
Nevertheless: even with an updated version which allocates only 14 surfaces (and thus avoiding said warning) the CPU usage is still way to high.
Could we please start focussing on the actual problem now?
comment:5 Changed 14 years ago by
| Ticket locked: | set |
|---|
See TicketHowTo. Forward further snide remarks to prescribed location.
mythfrontend logging