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

[RTMP] Fatal panic when calling the RTMP API while starting the stream at the same time #2430

Closed
4 of 13 tasks
p4xx07 opened this issue Sep 28, 2023 · 5 comments
Closed
4 of 13 tasks

Comments

@p4xx07
Copy link
Contributor

p4xx07 commented Sep 28, 2023

Which version are you using?

v1.1.0

Which operating system are you using?

  • Linux amd64 standard
  • Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

The application panics and there is no way of avoiding it. This happens when mediamtx receives a stream and in the same moment you ask the get streams api.
I've only tried with RTMP but this could also be the case with also the other protocols (srt, hls, webrtc, rtsp)
I'm guessing it's some kind of concurrency issue.
Please help because this issue is really critical for my use case, I need to get the status of the connections quite often and I can't have this issue in production. Thanks

Describe how to replicate the issue

  1. start the server
  2. publish a stream with rtmp
  3. call the http://localhost:9997/v2/rtmpconns/list API

Did you attach the server logs?

serverlogs.txt

yes

Did you attach a network dump?

no

@Allan-Nava
Copy link

+1

@p4xx07
Copy link
Contributor Author

p4xx07 commented Sep 28, 2023

image

When I remove the bytes received line I don't have the issue anymore. It's most likely some concurrency issue correlated to this (rtmp_conn.go line 648)

aler9 pushed a commit that referenced this issue Sep 28, 2023
Co-authored-by: Paxx <daniel.botta@hiway.media>
@aler9
Copy link
Member

aler9 commented Sep 28, 2023

fixed by #2431

@aler9 aler9 closed this as completed Sep 28, 2023
@aler9
Copy link
Member

aler9 commented Oct 15, 2023

added in v1.2.0

Copy link
Contributor

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants