Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: KVS SDK RTP retransmitter bug #1991

Open
3 tasks done
wei-zhang-simplisafe opened this issue May 21, 2024 · 2 comments
Open
3 tasks done

[Bug]: KVS SDK RTP retransmitter bug #1991

wei-zhang-simplisafe opened this issue May 21, 2024 · 2 comments
Assignees
Labels

Comments

@wei-zhang-simplisafe
Copy link

wei-zhang-simplisafe commented May 21, 2024

Please confirm you have already done the following

  • I have searched the repository for related/existing bug reports
  • I have all the details the issue requires

Please answer the following prompt

  • This issue is replicable using the unmodified sample application

Describe the bug

There is a bug at https://github.com/awslabs/amazon-kinesis-video-streams-webrtc-sdk-c/blob/master/src/source/PeerConnection/Retransmitter.c#L108

sequenceNumberList should be replaced by validIndexList

For RTC sequence number <= 65536, sequenceNumberList and validIndexList have the same value, the code still works.
At 2Mbps, after 300 seconds of livestreaming, KVS SDK will fail to put retransmited packets back into rolling buffer and the video quality could suffer.

Expected Behavior

Re-transmitter always works

Current Behavior

Re-transmitter fails after sending 65536 RTP packets

Reproduction Steps

after sending 65536 RTP packets, re-transmit will fail with STATUS_ROLLING_BUFFER_NOT_IN_RANGE

WebRTC C SDK version being used

latest as of 05/20/2024

If it was working in a previous version, which one?

No response

Compiler and Version used

all compilers

Operating System and version

all OS

Platform being used

all platform

@wei-zhang-simplisafe wei-zhang-simplisafe added bug Something isn't working needs-triage labels May 21, 2024
@wei-zhang-simplisafe
Copy link
Author

This ticket is exactly the same as #1453
The previous ticket was submitted two years ago. I am surprised that it was never fixed

@hassanctech
Copy link
Contributor

@wei-zhang-simplisafe I'm working on validating the finding, when I have an update I will post it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants