[GH-ISSUE #10739] Audio playback can get into an unstoppable state. #16013

New Issue

GiteaMirror · 2026-04-19T22:04:08-05:00

GiteaMirror commented

2026-04-19 22:04:08 -05:00

Originally created by @Zambito1 on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10739

Bug Report

Important Notes

Before submitting a bug report: Please check the Issues or Discussions section to see if a similar issue or feature request has already been posted. It's likely we're already tracking it! If you’re unsure, start a discussion post first. This will help us efficiently focus on improving the project.
Collaborate respectfully: We value a constructive attitude, so please be mindful of your communication. If negativity is part of your approach, our capacity to engage may be limited. We’re here to help if you’re open to learning and communicating positively. Remember, Open WebUI is a volunteer-driven project managed by a single maintainer and supported by contributors who also have full-time jobs. We appreciate your time and ask that you respect ours.
Contributing: If you encounter an issue, we highly encourage you to submit a pull request or fork the project. We actively work to prevent contributor burnout to maintain the quality and continuity of Open WebUI.
Bug reproducibility: If a bug cannot be reproduced with a :main or :dev Docker setup, or a pip install with Python 3.11, it may require additional help from the community. In such cases, we will move it to the "issues" Discussions section due to our limited resources. We encourage the community to assist with these issues. Remember, it’s not that the issue doesn’t exist; we need your help!

Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!

Installation Method

Docker

Environment

Open WebUI Version: 0.5.16
Operating System: Fedora 41
Browser (if applicable): Various versions of mobile (Android) and desktop Chromium and Firefox

Confirmation:

I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

I should always be able to stop audio playback.

Actual Behavior:

If I start text to speech playback within a chat, and navigate away from the chat while the playback is playing, there is no way to stop the audio playback anymore.

Description

Bug Summary:
Audio playback can get into a state where it cannot be stopped.

Reproduction Details

Steps to Reproduce:

Ask something that will give a fairly lengthy response using a non-temporary chat.
After the response finishes, click the button to play the response using TTS.
While the audio is playing, navigate away from the chat that is playing the audio. A new chat, a different existing chat, the admin settings page, etc.
Observe that the audio continues to play, but there is no longer a way to stop it. Returning to the original chat that has the message that is being played will no longer show the button to stop the audio.
In this state, clicking the play audio button on any message (including the message already being read) will result in both messages being read simultaneously.

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:
[Include relevant Docker container logs, if applicable]

Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Additional Information

It seems like a separate but related but that two messages can be played aloud simultaneously, but the main issue to me is that one message can be played multiple times simultaneously. Fixing this bug may include fixing the other though.

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Originally created by @Zambito1 on GitHub (Feb 25, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/10739 # Bug Report ## Important Notes - **Before submitting a bug report**: Please check the Issues or Discussions section to see if a similar issue or feature request has already been posted. It's likely we're already tracking it! If you’re unsure, start a discussion post first. This will help us efficiently focus on improving the project. - **Collaborate respectfully**: We value a constructive attitude, so please be mindful of your communication. If negativity is part of your approach, our capacity to engage may be limited. We’re here to help if you’re open to learning and communicating positively. Remember, Open WebUI is a volunteer-driven project managed by a single maintainer and supported by contributors who also have full-time jobs. We appreciate your time and ask that you respect ours. - **Contributing**: If you encounter an issue, we highly encourage you to submit a pull request or fork the project. We actively work to prevent contributor burnout to maintain the quality and continuity of Open WebUI. - **Bug reproducibility**: If a bug cannot be reproduced with a `:main` or `:dev` Docker setup, or a pip install with Python 3.11, it may require additional help from the community. In such cases, we will move it to the "issues" Discussions section due to our limited resources. We encourage the community to assist with these issues. Remember, it’s not that the issue doesn’t exist; we need your help! Note: Please remove the notes above when submitting your post. Thank you for your understanding and support! --- ## Installation Method Docker ## Environment - **Open WebUI Version:** 0.5.16 - **Operating System:** Fedora 41 - **Browser (if applicable):** Various versions of mobile (Android) and desktop Chromium and Firefox **Confirmation:** - [X] I have read and followed all the instructions provided in the README.md. - [X] I am on the latest version of both Open WebUI and Ollama. - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. - [X] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: I should always be able to stop audio playback. ## Actual Behavior: If I start text to speech playback within a chat, and navigate away from the chat while the playback is playing, there is no way to stop the audio playback anymore. ## Description **Bug Summary:** Audio playback can get into a state where it cannot be stopped. ## Reproduction Details **Steps to Reproduce:** - Ask something that will give a fairly lengthy response using a non-temporary chat. - After the response finishes, click the button to play the response using TTS. - While the audio is playing, navigate away from the chat that is playing the audio. A new chat, a different existing chat, the admin settings page, etc. - Observe that the audio continues to play, but there is no longer a way to stop it. Returning to the original chat that has the message that is being played will no longer show the button to stop the audio. - In this state, clicking the play audio button on any message (including the message already being read) will result in both messages being read simultaneously. ## Logs and Screenshots **Browser Console Logs:** [Include relevant browser console logs, if applicable] **Docker Container Logs:** [Include relevant Docker container logs, if applicable] **Screenshots/Screen Recordings (if applicable):** [Attach any relevant screenshots to help illustrate the issue] ## Additional Information It seems like a separate but related but that two messages can be played aloud simultaneously, but the main issue to me is that one message can be played multiple times simultaneously. Fixing this bug may include fixing the other though. ## Note If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

GiteaMirror added the bug label 2026-04-19 22:04:08 -05:00

GiteaMirror closed this issue

2026-04-19 22:04:09 -05:00

GiteaMirror commented

2026-04-19 22:04:10 -05:00

@delphiduan commented on GitHub (Mar 6, 2025):

When I use it in WeChat browser, I also encounter the issue of not being able to pause audio playback.

@delphiduan commented on GitHub (Mar 6, 2025): When I use it in WeChat browser, I also encounter the issue of not being able to pause audio playback.

GiteaMirror commented

2026-04-19 22:04:10 -05:00

@lee-b commented on GitHub (May 24, 2025):

I've seen (or heard) this too.

FYI, reloading the page is a workaround. Doesn't really help during no-keyboard voice calls though, which is a big part of the point.

@lee-b commented on GitHub (May 24, 2025): I've seen (or heard) this too. FYI, reloading the page is a workaround. Doesn't really help during no-keyboard voice calls though, which is a big part of the point.

GiteaMirror referenced this issue

2026-04-19 23:37:36 -05:00

[GH-ISSUE #16013] issue: Github api returning empty brackets (similar to #4494 but the request format is already set to default) #17752

GiteaMirror referenced this issue

2026-04-25 07:12:09 -05:00

[GH-ISSUE #16013] issue: Github api returning empty brackets (similar to #4494 but the request format is already set to default) #33281

GiteaMirror referenced this issue

2026-05-05 19:23:59 -05:00

[GH-ISSUE #16013] issue: Github api returning empty brackets (similar to #4494 but the request format is already set to default) #56418

Sign in to join this conversation.