[Bug]: the phone's battery drains rapidly and overheats severely. At this point, opening the Audiobookshelf app results in a blank screen. #585

New issue

Open

opened 2025-10-14 16:51:19 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:51:19 -06:00

Owner

Originally created by @zhuzhu88920 on 3/2/2025

What happened?

During normal playback of audiobooks on the iOS client, the phone's battery drains rapidly and overheats severely. At this point, opening the Audiobookshelf app results in a blank screen. After exiting and reopening the app, playback resumes normally, and the phone gradually cools down, with battery consumption returning to normal. However, this issue recurs after a while, particularly after the server was updated to version 2.19.5, when it becomes even more frequent.

What did you expect to happen?

fix bug

Steps to reproduce the issue

I am also unsure how to reproduce this issue.

Audiobookshelf version

0.9.79-beta

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?

None

Logs

Additional Notes

No response

*Originally created by @zhuzhu88920 on 3/2/2025* ### What happened? During normal playback of audiobooks on the iOS client, the phone's battery drains rapidly and overheats severely. At this point, opening the Audiobookshelf app results in a blank screen. After exiting and reopening the app, playback resumes normally, and the phone gradually cools down, with battery consumption returning to normal. However, this issue recurs after a while, particularly after the server was updated to version 2.19.5, when it becomes even more frequent. ### What did you expect to happen? fix bug ### Steps to reproduce the issue 1. I am also unsure how to reproduce this issue. ### Audiobookshelf version 0.9.79-beta ### 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? None ### Logs ```shell ``` ### Additional Notes _No response_