[Gstreamer-bugs] [Bug 143086] - GStreamer crashes with the artsd sink.

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=143086
GStreamer | don't know | Ver: 0.8.1





------- Additional Comments From t.i.m at zen.co.uk  2004-05-25 08:03 -------
Happens as well here, with up-to-date debian sid: 
 
sceptic [tim] - ~ ---> valgrind --num-callers=15 gst-launch-0.8 filesrc 
location=foo.mp3 ! mad ! spider ! artsdsink 
 
RUNNING pipeline ... 
artsdsink: closed connection 
 
 Invalid read of size 4 
    at 0x3CE2D36C: Arts::StartupManager::startup() 
(in /usr/lib/libmcop.so.1.0.0) 
    by 0x3CE13023: Arts::Dispatcher::Dispatcher(Arts::IOManager*, 
Arts::Dispatcher::StartServer) (in /usr/lib/libmcop.so.1.0.0) 
    by 0x3CAE2C74: arts_backend_init (in /usr/lib/libartscbackend.so.0.0.0) 
    by 0x3C969755: arts_init (in /usr/lib/libartsc.so.0.0.0) 
    by 0x3C14BDCD: gst_artsdsink_open_audio (gstartsdsink.c:296) 
    by 0x3C14B87E: gst_artsdsink_link (gstartsdsink.c:174) 
    by 0x3C05B8DE: gst_pad_link_call_link_functions (gstpad.c:1300) 
    by 0x3C05BD29: gst_pad_link_try (gstpad.c:1371) 
    by 0x3C938A92: gst_spider_identity_link (gstspideridentity.c:261) 
    by 0x3C05B8DE: gst_pad_link_call_link_functions (gstpad.c:1300) 
    by 0x3C05BD29: gst_pad_link_try (gstpad.c:1371) 
    by 0x3C938A92: gst_spider_identity_link (gstspideridentity.c:261) 
    by 0x3C05B8DE: gst_pad_link_call_link_functions (gstpad.c:1300) 
    by 0x3C05BD29: gst_pad_link_try (gstpad.c:1371) 
    by 0x3C060003: gst_pad_set_explicit_caps (gstpad.c:2480) 
  Address 0x3CB89DD4 is not stack'd, malloc'd or free'd 
 
 Process terminating with default action of signal 11 (SIGSEGV): dumping core 
  Access not within mapped region at address 0x3CB89DD4 
    at 0x3CE2D36C: Arts::StartupManager::startup() 
(in /usr/lib/libmcop.so.1.0.0) 
    by 0x3CE13023: Arts::Dispatcher::Dispatcher(Arts::IOManager*, 
Arts::Dispatcher::StartServer) (in /usr/lib/libmcop.so.1.0.0) 
    by 0x3CAE2C74: arts_backend_init (in /usr/lib/libartscbackend.so.0.0.0) 
    by 0x3C969755: arts_init (in /usr/lib/libartsc.so.0.0.0) 
    by 0x3C14BDCD: gst_artsdsink_open_audio (gstartsdsink.c:296) 
    by 0x3C14B87E: gst_artsdsink_link (gstartsdsink.c:174) 
    by 0x3C05B8DE: gst_pad_link_call_link_functions (gstpad.c:1300) 
    by 0x3C05BD29: gst_pad_link_try (gstpad.c:1371) 
    by 0x3C938A92: gst_spider_identity_link (gstspideridentity.c:261) 
    by 0x3C05B8DE: gst_pad_link_call_link_functions (gstpad.c:1300) 
    by 0x3C05BD29: gst_pad_link_try (gstpad.c:1371) 
    by 0x3C938A92: gst_spider_identity_link (gstspideridentity.c:261) 
    by 0x3C05B8DE: gst_pad_link_call_link_functions (gstpad.c:1300) 
    by 0x3C05BD29: gst_pad_link_try (gstpad.c:1371) 
    by 0x3C060003: gst_pad_set_explicit_caps (gstpad.c:2480) 
 
Segmentation fault (core dumped) 
 
 
However, when run like this: 
 
sceptic [tim] - ~ ---> gst-launch-0.8 filesrc location=foo.mp3 ! mad ! 
artsdsink 
RUNNING pipeline ... 
artsdsink: closed connection 
Segmentation fault (core dumped) 
 
it also segfaults, but not when run with valgrind: 
 
sceptic [tim] - ~ ---> valgrind --num-callers=15 gst-launch-0.8 filesrc 
location=xaa.mp3 ! mad ! artsdsink 
 
**29892** GStreamer has detected that it is running inside valgrind. 
**29892** It might now take different code paths to ease debugging. 
**29892** Of course, this may also lead to different bugs. 
 
RUNNING pipeline ... 
artsdsink: closed connection 
 
.... long time of nothing happening ..... 
 
Execution ended after 65 iterations (sum 19756033000 ns, average 303938969 ns, 
min 20790000 ns, max 3992515000 ns). 
warning: leaving MCOP Dispatcher and still 146 types alive. 
artsdsink: closed connection 
 
Same thing with filesrc ! mad ! audioconvert ! artsdsink  (e.g. no crash or 
warnings in valgrind, but crash without valgrind) 
 
Can't get any useful stack trace with gdb. 
 
Cheers 
-Tim 
 

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.