After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 539783 - BadAlloc when compositing is turned on
BadAlloc when compositing is turned on
Status: RESOLVED NOTGNOME
Product: totem
Classification: Core
Component: general
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-06-23 17:05 UTC by Federico Mena Quintero
Modified: 2008-06-25 21:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Federico Mena Quintero 2008-06-23 17:05:00 UTC 
This started as https://bugzilla.novell.com/show_bug.cgi?id=402683

With metacity compositing turned on (from gconf), trying to play a video with
totem, banshee-1, vlc, mplayer, ... result in a crash:

totem movie.ogg 
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 50 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Comment 1 Bastien Nocera 2008-06-23 17:06:31 UTC 
This is a bug in the device driver, not in Totem. Thanks!
Comment 2 Federico Mena Quintero 2008-06-25 20:25:33 UTC 
BadAlloc means some request couldn't be satisfied.  Should't Totem handle this?

Or if it's a bug in the X driver, do you know which bug in particular (from fd.o)?
Comment 3 Bastien Nocera 2008-06-25 21:03:35 UTC 
There's a GStreamer bug opened somewhere about xvimagesink/ximagesink handling better the first frame showed causing a BadAlloc.

But the problem usually is in the video driver(s) causing those in error in the first place. If you don't have patched versions of the drivers, it will happen for at least intel and ati drivers, that I know of. Talk to your X maintainers, the drivers in Fedora are all fixed up, AFAIK.