GNOME Bugzilla – Bug 756029
xvimagesink: can't create image: could not get shared memory of 3354624 bytes on OpenBSD
Last modified: 2016-05-22 17:01:25 UTC
Since upgrading from GStreamer 1.4 to 1.6 I am seeing video content using the Matroska container failing to playback. $ gst-play-1.0 Aliens-1080p.mkv Press 'k' to see a list of keyboard shortcuts. Now playing /Multimedia/Movies/Aliens-1080p.mkv Redistribute latency... ERROR GStreamer encountered a general stream error. for file:///Multimedia/Movies/Aliens-1080p.mkv ERROR debug information: matroska-demux.c(4637): gst_matroska_demux_loop (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstMatroskaDemux:matroskademux0: stream stopped, reason error Reached end of play list.
Could you run: $ GST_DEBUG=*:6 gst-play-1.0 Aliens-1080p.mkv 2>dbg.log $ xz -9 dbg.log and attach dbg.log.xz please? Thanks!
Created attachment 312644 [details] debug log file
0:00:07.380855000 [333m 3674[00m 0x8346ee6ad90 [33;01mWARN [00m [00m xvimagepool xvimagepool.c:199:xvimage_buffer_pool_alloc:<xvimagebufferpool2>[00m can't create image This is the original problem here it seems.
And unfortunately we don't know why because of: http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=19d714fa2f95f67c9ad94db7c359a1c7affe40d4
But basically it means shmget() or similar fails to allocate the XVImage, which might be just a problem on your setup. What's the output of xvinfo? Does anything else work with xvimagesink, or other software with XV output?
X-Video Extension version 2.2 screen #0 Adaptor #0: "Intel(R) Textured Video" number of ports: 16 port base: 75 operations supported: PutImage supported visuals: depth 24, visualID 0x20 number of attributes: 1 "XV_SYNC_TO_VBLANK" (range -1 to 1) client settable attribute client gettable attribute (current value is 1) maximum XvImage size: 16384 x 16384 Number of image formats: 5 id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x32315659 (YV12) guid: 59563132-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x30323449 (I420) guid: 49343230-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x434d5658 (XVMC) guid: 58564d43-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) Adaptor #1: "Intel(R) Video Sprite" number of ports: 1 port base: 91 operations supported: PutImage supported visuals: depth 24, visualID 0x20 number of attributes: 2 "XV_COLORKEY" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 66046) "XV_ALWAYS_ON_TOP" (range 0 to 1) client settable attribute client gettable attribute (current value is 0) maximum XvImage size: 8192 x 8192 Number of image formats: 3 id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x18424752 guid: 50415353-5448-524f-5547-485247423234 bits per pixel: 32 number of planes: 1 type: RGB (packed) depth: 24 red, green, blue masks: 0xff0000, 0xff00, 0xff I can play various other container / codec combos just fine with gst-play. I can play the same file(s) that are having issues with gst-play with MPlayer and MPV using XV.
Created attachment 312648 [details] debug log file
Looks like a problem on your system somehow: 0:00:04.711135000 28298 0xf6dcc880990 WARN xvimagepool xvimagepool.c:200:xvimage_buffer_pool_alloc:<xvimagebufferpool2> can't create image: could not get shared memory of 3354624 bytes shmget() fails.
No idea what else to do here, someone on OpenBSD would need to debug this and understand how and why X11 behaves different on OpenBSD than elsewhere.
If this still happens, can you see if reverting (or applying, if your tree doesn't have it) 964ea678dafcf4c2ad022e4c6f9948e3cec902fa fixes this ?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!