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!
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:
When the large model generates a response containing code blocks, Open WebUI should display the response normally without freezing, and all buttons should function as expected.
Actual Behavior:
When the large model generates a response containing code blocks, Open WebUI freezes. All buttons become unresponsive, and the response stops being displayed. After refreshing the page, the response is displayed, but the code blocks are not viewable, and the buttons remain unresponsive. Changing the URL and refreshing again temporarily resolves the issue, but accessing the page with code blocks again causes it to freeze.
Description
Bug Summary: Open WebUI freezes and becomes unresponsive when displaying responses containing code blocks, preventing further interaction and proper rendering of the content.
Reproduction Details
Steps to Reproduce:
Use the large model to generate a response that includes code blocks.
Observe that Open WebUI freezes and buttons become unresponsive.
Refresh the page; the response is displayed, but code blocks are not viewable, and buttons remain unresponsive.
Change the URL and refresh again; the issue is temporarily resolved.
Access the page with code blocks again, causing the freeze to reoccur.
Docker Container Logs: [Include relevant Docker logs, if applicable]
Screenshots/Screen Recordings (if applicable):
Everything worked fine at the beginning.
Various buttons are stuck.
After Refresh
Code blocks cannot be viewed.
Various buttons are stuck.
Additional Information
I don't know what to fill in, I'm using the OpenAI-compatible API provided by Text-Generation-WebUI.
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 @At87668 on GitHub (Feb 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9235
# 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
git clone https://github.com/open-webui/open-webui.git
cd open-webui
pnpm install
pnpm build
cd backend
pip install -r requirements.txt
## Environment
- **Open WebUI Version:** [v0.5.7]
- **Ollama (if applicable):** []
- **Operating System:** [Windows 11]
- **Browser (if applicable):** [Edge 129.0.2792.65] **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:
When the large model generates a response containing code blocks, Open WebUI should display the response normally without freezing, and all buttons should function as expected.
## Actual Behavior:
When the large model generates a response containing code blocks, Open WebUI freezes. All buttons become unresponsive, and the response stops being displayed. After refreshing the page, the response is displayed, but the code blocks are not viewable, and the buttons remain unresponsive. Changing the URL and refreshing again temporarily resolves the issue, but accessing the page with code blocks again causes it to freeze.
## Description
**Bug Summary:** Open WebUI freezes and becomes unresponsive when displaying responses containing code blocks, preventing further interaction and proper rendering of the content.
## Reproduction Details
**Steps to Reproduce:**
1. Use the large model to generate a response that includes code blocks.
2. Observe that Open WebUI freezes and buttons become unresponsive.
3. Refresh the page; the response is displayed, but code blocks are not viewable, and buttons remain unresponsive.
4. Change the URL and refresh again; the issue is temporarily resolved.
5. Access the page with code blocks again, causing the freeze to reoccur.
## Logs and Screenshots
**Browser Console Logs:** https://pastebin.com/WiapzxjB
**Docker Container Logs:** [Include relevant Docker logs, if applicable]
**Screenshots/Screen Recordings (if applicable):**
Everything worked fine at the beginning.


Various buttons are stuck.
After Refresh

Code blocks cannot be viewed.

Various buttons are stuck.
## Additional Information
I don't know what to fill in, I'm using the OpenAI-compatible API provided by Text-Generation-WebUI.
------
## 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!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @At87668 on GitHub (Feb 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9235
Bug Report
Important Notes
:mainor:devDocker 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
git clone https://github.com/open-webui/open-webui.git
cd open-webui
pnpm install
pnpm build
cd backend
pip install -r requirements.txt
Environment
Expected Behavior:
When the large model generates a response containing code blocks, Open WebUI should display the response normally without freezing, and all buttons should function as expected.
Actual Behavior:
When the large model generates a response containing code blocks, Open WebUI freezes. All buttons become unresponsive, and the response stops being displayed. After refreshing the page, the response is displayed, but the code blocks are not viewable, and the buttons remain unresponsive. Changing the URL and refreshing again temporarily resolves the issue, but accessing the page with code blocks again causes it to freeze.
Description
Bug Summary: Open WebUI freezes and becomes unresponsive when displaying responses containing code blocks, preventing further interaction and proper rendering of the content.
Reproduction Details
Steps to Reproduce:
Logs and Screenshots
Browser Console Logs: https://pastebin.com/WiapzxjB
Docker Container Logs: [Include relevant Docker logs, if applicable]
Screenshots/Screen Recordings (if applicable):
Everything worked fine at the beginning.
Various buttons are stuck.
After Refresh
Code blocks cannot be viewed.
Various buttons are stuck.
Additional Information
I don't know what to fill in, I'm using the OpenAI-compatible API provided by Text-Generation-WebUI.
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!