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
Possible 100% CPU usage by a background thread with FFmpeg 4.2 and GnuTLS #239
Labels
Comments
|
To workaround this issue on Arch Linux or Manjaro Linux, please use |
|
Already fixed on ffmpeg master. |
|
FFmpeg 4.3.1 is already available in Arch Linux repository. |
|
This issue is for GnuTLS (not used on Windows, Linux only), FFmpeg 4.2.x only and special case when connection is aborted on connecting state. I need more details, maybe create a new issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Aborting FFmpeg GnuTLS connection causes infinity loop inside libavformat library. When changing entries on QMPlay2 playlist background, LastFM connection for covers can be aborted causing 100% CPU usage by a background thread. In this case QMPlay2 needs to be closed.
This is regression found in 4.2 version.
See:
https://trac.ffmpeg.org/ticket/8080
https://patchwork.ffmpeg.org/patch/14550/
The text was updated successfully, but these errors were encountered: