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 432036 - X error (BadAlloc) when trying to play back a wmv file
X error (BadAlloc) when trying to play back a wmv file
Status: RESOLVED DUPLICATE of bug 351784
Product: totem
Classification: Core
Component: GStreamer backend
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2007-04-21 17:15 UTC by Kjartan Maraas
Modified: 2007-04-24 13:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Kjartan Maraas 2007-04-21 17:15:56 UTC 
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 47 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.)

(gdb) bt full

+ Trace 129559

  • #0 gdk_x_error
    at gdkmain-x11.c line 614
  • #1 ??
    from /usr/lib/libbonoboui-2.so.0
  • #2 _XError
    from /usr/lib/libX11.so.6
  • #3 _XReply
    from /usr/lib/libX11.so.6
  • #4 XSync
    from /usr/lib/libX11.so.6
  • #5 gst_xvimagesink_xvimage_put
    at xvimagesink.c line 790
  • #6 gst_xvimagesink_show_frame
    at xvimagesink.c line 2141
  • #7 gst_base_sink_queue_object_unlocked
    at gstbasesink.c line 1779
  • #8 gst_base_sink_chain_unlocked
    at gstbasesink.c line 2120
  • #9 gst_base_sink_chain
    at gstbasesink.c line 2154
  • #10 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #11 gst_pad_push
    at gstpad.c line 3625
  • #12 gst_proxy_pad_do_chain
    at gstghostpad.c line 191
  • #13 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #14 gst_pad_push
    at gstpad.c line 3625
  • #15 gst_proxy_pad_do_chain
    at gstghostpad.c line 191
  • #16 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #17 gst_pad_push
    at gstpad.c line 3625
  • #18 gst_base_transform_chain
    at gstbasetransform.c line 1571
  • #19 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #20 gst_pad_push
    at gstpad.c line 3625
  • #21 gst_base_transform_chain
    at gstbasetransform.c line 1571
  • #22 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #23 gst_pad_push
    at gstpad.c line 3625
  • #24 gst_base_transform_chain
    at gstbasetransform.c line 1571
  • #25 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #26 gst_pad_push
    at gstpad.c line 3625
  • #27 gst_proxy_pad_do_chain
    at gstghostpad.c line 191
  • #28 gst_pad_chain_unchecked
    at gstpad.c line 3459
  • #29 gst_pad_push
    at gstpad.c line 3625
  • #30 gst_queue_loop
    at gstqueue.c line 810
  • #31 gst_task_func
    at gsttask.c line 192
  • #32 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #33 g_thread_create_proxy
    at gthread.c line 591
  • #34 start_thread
    from /lib/libpthread.so.0
  • #35 clone
    from /lib/libc.so.6 
(gdb) quit
Comment 1 Kjartan Maraas 2007-04-21 17:16:51 UTC 
Xine says this when playing the same file:

[wmv2 @ 0x1318564]J-type picture is not supported
[wmv2 @ 0x1318564]J-type picture is not supported
[wmv2 @ 0x1318564]J-type picture is not supported
[wmv2 @ 0x1318564]J-type picture is not supported
[wmv2 @ 0x1318564]J-type picture is not supported
[wmv2 @ 0x1318564]J-type picture is not supported

And mplayer cannot play it either. I guess fixing totem so it doesn't "crash" is reasonable anyway.
Comment 2 Tim-Philipp Müller 2007-04-24 13:19:07 UTC 
The J-type picture stuff is from the ffmpeg windows media decoder; it might cause artefacts in the movie, but that should be all.

I think the _put() error is something else (possibly a video driver bug, not sure). In any case, looks like bug #351784.

*** This bug has been marked as a duplicate of 351784 ***