From 8b44f324358f10b1809366b00a34369ed99c6ec2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= Date: Fri, 25 Oct 2019 02:02:59 +0300 Subject: [PATCH] Return gst::BusSyncReply::Drop from the bus sync handler in the Rust sendrecv example Otherwise all messages accumulate on the queue inside the bus and nothing is ever removing them from there. We handle messages elsewhere and only intercept them from the sync handler. --- webrtc/sendrecv/gst-rust/src/main.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/webrtc/sendrecv/gst-rust/src/main.rs b/webrtc/sendrecv/gst-rust/src/main.rs index 83dfe3ed8d..01e8e5fc46 100644 --- a/webrtc/sendrecv/gst-rust/src/main.rs +++ b/webrtc/sendrecv/gst-rust/src/main.rs @@ -819,7 +819,7 @@ fn main() { let send_gst_msg_tx = Mutex::new(send_gst_msg_tx); bus.set_sync_handler(move |_, msg| { let _ = send_gst_msg_tx.lock().unwrap().try_send(msg.clone()); - gst::BusSyncReply::Pass + gst::BusSyncReply::Drop }); // Create our application control logic