GNOME Bugzilla – Bug 745557
Crash when printing debug message
Last modified: 2016-02-22 00:19:51 UTC
When setting debug level to 5 on android, I get this crash:
+ Trace 234772
Thread 25 (Thread 1721)
Thread 24 (Thread 1720)
Thread 23 (Thread 1719)
Thread 22 (Thread 1718)
Thread 21 (Thread 1713)
Thread 20 (Thread 1711)
Thread 19 (Thread 1710)
Thread 18 (Thread 1693)
Thread 17 (Thread 1692)
Thread 15 (Thread 1660)
Thread 14 (Thread 1658)
Thread 13 (Thread 1656)
Thread 12 (Thread 1655)
Thread 11 (Thread 1654)
Thread 10 (Thread 1653)
Thread 9 (Thread 1652)
Thread 8 (Thread 1651)
Thread 6 (Thread 1649)
Thread 5 (Thread 1648)
Thread 4 (Thread 1647)
Thread 3 (Thread 1709)
Crash is in thread 3.
Do you have a testcase, and can you reproduce it outside Android too? Can you run it in a debugger and check what the value of "queue" at gstqueue2.c:927 is? This only seems possible if there is a reference counting problem somewhere, and the queue is already dead at that point.
I could not reproduce here with a simple playback app.
Not sure what to do about this, and we don't even know what exact version this happened with. I wonder if this is fixed by: commit 6c394643be52dc525af6b21b3ba7f014eea0eb7f Author: Tim-Philipp Müller <tim@centricular.com> Date: Fri Apr 24 15:16:24 2015 +0100 printf: fix invalid memory access in case of %% https://bugzilla.gnome.org/show_bug.cgi?id=748414 Since the only debug message I can see in post_buffering() is GST_DEBUG_OBJECT (queue, "Going to post buffering: %d%%", percent); Anyway, I think we'll have to close this without further information to go on. Please re-open if you have a test case or can still reproduce it somehow.