Bug 692014 – Assertion hit in gst_buffer_pool_acquire_buffer()

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 692014 - Assertion hit in gst_buffer_pool_acquire_buffer()


Summary:	Assertion hit in gst_buffer_pool_acquire_buffer()


Status:	RESOLVED INCOMPLETE

Product:	GStreamer
Classification:	Platform
Component:	gst-plugins-base
Version:	1.0.5
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	NONE
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-01-18 14:54 UTC by Christophe Dumez
Modified:	2016-02-21 22:30 UTC

See Also:	https://bugs.webkit.org/show_bug.cgi?id=106551
GNOME target:	---
GNOME version:	---

Attachments
Log with GST_DEBUG=3 (36.58 KB, text/plain) 2013-01-20 21:11 UTC, Christophe Dumez	Details
Log with GST_DEBUG=4 (319.43 KB, text/plain) 2013-01-20 21:22 UTC, Christophe Dumez	Details

Description Christophe Dumez 2013-01-18 14:54:24 UTC

We sometimes hit the following assertion when running the media tests in WebKit:
(WebProcess:15781): GStreamer-CRITICAL **: gst_buffer_pool_acquire_buffer: assertion `GST_IS_BUFFER_POOL (pool)' failed

Program received signal SIGTRAP, Trace/breakpoint trap.

+ Trace 231394

Thread 140735340869376 (LWP 16568)

#0 g_logv
at gmessages.c line 765
#1 g_log
at gmessages.c line 792
#2 gst_buffer_pool_acquire_buffer
at gstbufferpool.c line 1090
#3 gst_video_decoder_allocate_output_frame
at gstvideodecoder.c line 3112
#4 get_output_buffer
at gstavviddec.c line 1000
#5 gst_ffmpegviddec_video_frame
at gstavviddec.c line 1188
#6 gst_ffmpegviddec_frame
at gstavviddec.c line 1262
#7 gst_ffmpegviddec_handle_frame
at gstavviddec.c line 1379
#8 gst_video_decoder_decode_frame
at gstvideodecoder.c line 2665
#9 gst_video_decoder_chain_forward
#10 gst_video_decoder_chain
at gstvideodecoder.c line 1957
#11 gst_pad_chain_data_unchecked
at gstpad.c line 3654
#12 gst_pad_push_data
at gstpad.c line 3871
#13 gst_pad_push
at gstpad.c line 3974
#14 gst_base_transform_chain
at gstbasetransform.c line 2203
#15 gst_pad_chain_data_unchecked
at gstpad.c line 3654
#16 gst_pad_push_data
at gstpad.c line 3871
#17 gst_pad_push
at gstpad.c line 3974
#18 gst_base_parse_push_frame
at gstbaseparse.c line 2146
#19 gst_base_parse_chain
at gstbaseparse.c line 2623
#20 gst_pad_chain_data_unchecked
at gstpad.c line 3654
#21 gst_pad_push_data
at gstpad.c line 3871
#22 gst_pad_push
at gstpad.c line 3974
#23 gst_single_queue_push_one
at gstmultiqueue.c line 1057
#24 gst_multi_queue_loop
at gstmultiqueue.c line 1303
#25 gst_task_func
at gsttask.c line 316
#26 default_func
at gsttaskpool.c line 70
#27 g_thread_pool_thread_proxy
at gthreadpool.c line 309
#28 g_thread_proxy
at gthread.c line 801
#29 start_thread
at pthread_create.c line 308
#30 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
#31 ??


Note that this crash happens randomly and I do not have a reliable way of reproducing it at the moment.

Comment 1 Tim-Philipp Müller 2013-01-20 18:16:07 UTC

Any chance you could provide a GST_DEBUG=*:6 log for this as well? (compressed with xz -9 or so if needed)

Comment 2 Christophe Dumez 2013-01-20 18:22:02 UTC

I will try but I am having more trouble reproducing this one so far.

Comment 3 Christophe Dumez 2013-01-20 21:11:01 UTC

Created attachment 233963 [details]
Log with GST_DEBUG=3

Attaching log with GST_DEBUG=3. I haven't been able to reproduce with more verbose logging yet.

Comment 4 Christophe Dumez 2013-01-20 21:22:38 UTC

Created attachment 233964 [details]
Log with GST_DEBUG=4

Comment 5 Sebastian Dröge (slomo) 2014-01-20 14:31:06 UTC

Does this still happen with 1.2.2 and latest gst-libav?

Comment 6 Tim-Philipp Müller 2016-02-21 22:30:49 UTC

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!

(Stack trace looks familiar, there's a good chance this has been fixed fwiw.)