Skip to content

fix/subscription and event buffer follow ups - #26

Merged
dangusev merged 4 commits into
fix/pacer-and-resampler-follow-upsfrom
fix/subscription-and-event-buffer-follow-ups
Oct 13, 2026
Merged

dangusev merged 4 commits into
fix/pacer-and-resampler-follow-upsfrom
fix/subscription-and-event-buffer-follow-ups

Conversation

@dangusev

Copy link
Copy Markdown
Collaborator

Stack created with GitHub Stacks CLI • Give Feedback 💬

@dangusev
dangusev added this pull request to stack #31 October 13, 2026 14:22
@dangusev
dangusev force-pushed the fix/subscription-and-event-buffer-follow-ups branch 2 times, most recently from 2c2d055 to 57e6316 Compare October 13, 2026 14:54
SubscriptionConfig::default() now subscribes to nothing, and the call started from it. Before an update_subscriptions call, set_incoming_video_enabled(true) gave video only, and false gave nothing, with no error. The call now starts from audio_all, as on main, so true gives audio and video and false gives audio only. JS setIncomingVideoEnabled also never removes audio.
Each call allocates all slots of three broadcast channels, about 464 B for each unit of capacity. A large value that passed the old check (tokio's panic bound) aborted the process at call creation. Client::new now returns Error::Config for a value above 65,536, which costs about 30 MiB for each call.
@dangusev
dangusev force-pushed the fix/subscription-and-event-buffer-follow-ups branch from 57e6316 to c33d00f Compare October 13, 2026 15:02
@dangusev
dangusev merged commit 8fff194 into main Oct 13, 2026
6 of 11 checks passed
@dangusev
dangusev deleted the fix/subscription-and-event-buffer-follow-ups branch October 13, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants