BadAlloc when using xv on nv driver

Bug #12660 reported by Ruben Vermeersch
8
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Medium
Ubuntu-X

Bug Description

When trying to use mplayer or totem-xine in combination with the nv driver, they
fail with the following error:

MPlayer interrupted by signal 6 in module: uninit_vo
X Error of failed request: BadAlloc (insufficient resources for operation)
  Major opcode of failed request: 142 (XVideo)
  Minor opcode of failed request: 19 ()
  Serial number of failed request: 98
  Current serial number in output stream: 102

This appears to be an X bug as I've found this one:
http://freedesktop.org/bugzilla/show_bug.cgi?id=474

Though they say it should be fixed, my nv driver still fails on this one. I'd
rather not use the binary nvidia driver as it breaks suspend support.

https://bugs.freedesktop.org/show_bug.cgi?id=474: https://bugs.freedesktop.org/show_bug.cgi?id=474

Revision history for this message
Daniel Stone (daniels) wrote :

As Egbert's last comment says, has it ever worked with other combinations of
software? It might be that your system actually lacks the video RAM to do large
videos.

Revision history for this message
Ruben Vermeersch (ruben) wrote :

When using the binary nvidia drivers, all works well, I'm having a 6 months old
laptop with a nVidia® GeForce FX Go5200, which should be sufficient, I think?

Revision history for this message
Daniel Stone (daniels) wrote :

Could you please supply /var/log/Xorg.0.log?

Revision history for this message
Ruben Vermeersch (ruben) wrote :

Created an attachment (id=1429)
Xorg Log

Revision history for this message
Ruben Vermeersch (ruben) wrote :

Created an attachment (id=1430)
Xsession-errors

Revision history for this message
Daniel Stone (daniels) wrote :

Thanks, have pushed all this information upstream.

Revision history for this message
Marc Wiriadisastra (strikeforce) wrote :

I have the same issues apparently this had been fixed or it might be fixed
already. According to this that is.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126307 I run a base breezy
have all of the plugins installed and I can't view a .ogg file that I created
using istanbul.

I use the generic video drivers from ubuntu.
Section "Device"
        Identifier "Intel Corporation 82852/855GM Integrated Graphics Device"
        Driver "i810"
        BusID "PCI:0:2:0"
EndSection

Its on a laptop and I get the same error when viewing it. I think this might
also link into the bug relating to firefox crashing when totem is trying to play
videos since that was my original bug post before I noticed this.

Revision history for this message
Marc Wiriadisastra (strikeforce) wrote :

I tried it specifically calling -vo x11 instead of -vo xv and its working so I'm
not sure where the issue is now?

e.g. mplayer -vo x11 desktop-recording.ogg

Daniel Stone (daniels)
Changed in xorg:
assignee: daniels → nobody
Revision history for this message
Matt Zimmerman (mdz) wrote :

Is this problem still present in current Dapper?

Changed in xorg:
status: Unconfirmed → Needs Info
Revision history for this message
Joe Van Dyk (joevandyk) wrote :

I'm using the i810 driver with a i950 graphics card (in my dell e1505 notebook). On high resolution videos, playing them in mplayer, vlc, and totem all crash. I've got 65MB of video memory allocated.

Playing them with mplayer's x11 instead of xv works great though (but slow).

Revision history for this message
Carthik Sharma (carthik) wrote :

Confirming this and assigning to ubuntu-x-swat.

Thank for reporting on this issue.

Changed in xorg:
assignee: nobody → ubuntu-x-swat
status: Needs Info → Confirmed
Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

No info from the submitter after Matt request. I also use this combination and it works just fine in dapper.

Fabio

Changed in xorg:
status: Confirmed → Rejected
Revision history for this message
yoeloosh (yoeloosh) wrote :

i have the same problam with different video card
Section "Device"
        Identifier "S3 Inc. Savage 4"
        Driver "savage"
        BusID "PCI:1:0:

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.