I can send backtrace but the first warning fired is about a loop in the graph, which 
is logical, here is the content of my bin, bin used to transcode RTP streams ::
				    audiotestsrc0
                                                 \                      
                                                  adder0 -> queue0 -> identity0 -> encoder0 -> rtppayloader0 -> rtpmux0
                      rtpdepayloader0 -> decoder0 /                                                                     \
                     /                                                                                                   \
<=in/out RTP=> rtpbin0                                                                                                   rtpbin1 <=in/out RTP=> 
                     \                                                                                                  /
                      \                                                                      decoder1 <- rtpdepayloader1
                       \                                                                    /
                       rtpmux1 <- rtppayloader1 <- encoder1 <- identity1 <- queue1 <- adder1 
                                                                                            \
                                                                                              audiotestsrc1

rtpbin (the one from gst-plugins-farsight) is used to receive AND send rtp. some parts of the pipeline are dynamically
linked on new RTP payload received (depayloader + decoder)

The application is quite large and multithreaded (not only Gstreamer ones), 
do you prefer backtrace for warning of detected loop, backtrace of the first Critical event (due to using 
unreffed element) (previous loop in graph warning disabled) or both.


