mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Kill the audiobookshelf process that is currently playing on Android; the FFMPEG process on the server cannot be killed #2554
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JinLiGame on GitHub (Feb 7, 2025).
What happened?
Kill the audiobookshelf process that is currently playing on Android; the FFMPEG process on the server cannot be killed; however, clicking 'Close Player' normally terminates the FFMPEG process.
What did you expect to happen?
When the client is no longer playing, it should be able to kill the FFMPEG process and release the CPU.
Steps to reproduce the issue
Audiobookshelf version
2.19.0
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Other (list in "Additional Notes" box)
Logs
Additional Notes
In this log file, I first used 'Close Player' to stop the playback, and it showed '[FFMPEG] Transcode Killed'. Then, I tried to stop the playback by killing the client process, but it did not show '[FFMPEG] Transcode Killed'.
@gmile commented on GitHub (Jul 20, 2025):
Not sure if related, but I just I witnessed my homelab server's cooler start making an audible noise, went to check the logs and discovered this was related to
audiobookshelfstarting some transcoding work out of the blue.Here are the logs - you can clearly see some interaction with audiobookshelf I had during the morning, before a very random work started around
16:32.Did my Android app in the background requested something from the server to cause this? 🤔 If so, how can I make Android app stop doing what it was doing? In my case I didn't have that many files to process, so I just waited to this "Check files..." to finish some 10 minutes later.
@advplyr commented on GitHub (Jul 20, 2025):
Abs automatically falls back to transcoding the audiobook to an HLS stream when the device cannot direct play the audio file.
In this case the OP was playing a WMA file on android which is not supported so Abs transcodes to HLS
@gmile commented on GitHub (Jul 20, 2025):
@advplyr I see. Then my issue is not related (or related only mildly). In my case, the primary issue is that something started to happen without me actively using the application (android) or server UI. Feel free to mark my comment as out of topic, I will create a separate discussing for this 🤔
Upd. marked as off-topic myself and moved to https://github.com/advplyr/audiobookshelf/discussions/4514