In retry state, library creates too many NetStream Status updates.
Open
Nobody has claimed this yet.
- Dominant language
- ActionScript
- Stars
- 744
- Forks
- 259
- PR merge metrics
- No merged PRs in 30d
Description
If segment isn't available, and library retries to download it.
I can see many `NetStream.Pause.Notify`, nearly every 100-500 ms, until all retries will be finished.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a segment-unavailable download and observe the retry sequence and NetStream.Pause.Notify events. Trace where status updates are emitted during retries; done means retries complete without producing repeated updates every 100–500 ms.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100