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 416609 - Sound juicer crashes in gst_base_src_loop()
Sound juicer crashes in gst_base_src_loop()
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.10
Other Linux
: Normal critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-09 22:55 UTC by Sebastien Bacher
Modified: 2008-01-10 16:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2007-03-09 22:55:51 UTC 
The bug has been described on https://launchpad.net/bugs/89479

"Binary package hint: sound-juicer

Couldn't reproduce, but firefox was open with multiple tabs while ripping cd. And the computer had been in use for about 90 minutes.

Same conditions after reboot worked fine.
...
http://librarian.launchpad.net/6607638/_usr_bin_sound-juicer.1000.crash
Crash Report
...
 libgstreamer0.10-0 0.10.10-1ubuntu2
..."

Debug backtrace for the crash:

1459      src->priv->last_sent_eos = FALSE;
(gdb) thread apply all bt full

+ Trace 117311

Thread 1 (process 8508)

  • #0 gst_base_src_loop
    at gstbasesrc.c line 1459
  • #1 gst_task_func
    at gsttask.c line 192
  • #2 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #3 g_thread_create_proxy
    at gthread.c line 553
  • #4 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


Jan Schmidt





          2007-03-12 14:31:21 UTC
        



I'm not sure how we'd get to here - it implies that the loop was still running after the pad was removed from the element (gst_pad_get_parent returned NULL).

Maybe the element got unreffed too many times, or a garbage collecter caused dispose to be run? It's either that or memory corruption in an unrelated place afaics.






Comment 2


Tim-Philipp Müller





          2007-09-23 11:09:18 UTC
        



I agree with Jan.  If it's a refcounting bug, then there should have been a warning message printed to stderr - can you see anything like this in the submitted report?

In any case, I'm not sure what we can do about this without more info or a way to reproduce the problem.







Comment 3


Tim-Philipp Müller





          2008-01-10 16:40:31 UTC
        



Closing this as OBSOLETE as it refers to core+base 0.10.10 which is ancient.  If it's still a problem, someone will surely reproduce it with a newer version some day.