github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

UI Lockup on Message Interaction #2233

New Issue
Closed
opened 2025-11-11 15:03:05 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 15:03:05 -06:00
Owner
Copy Link

Originally created by @chrisoutwright on GitHub (Sep 28, 2024).

Bug Report: UI Lockup on Message Interaction

Installation Method

  • Method used: Manual for Win10

Environment

  • Open WebUI Version: v0.3.28
  • Ollama Version: v0.3.11
  • Operating System: Windows 10
  • Browser: Version 129.0.6668.71 (Official Build) (64-bit) , also tried on Edge with same behaviour.

Confirmation:

  • I have read and followed all 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 provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior

The chat message should be clickable, allowing interaction without causing the browser to freeze or CPU to spike.

Actual Behavior

When clicking on a specific message (ID: 6fee83cf-52c6-4c20-bc44-390858f2e848), the UI freezes, and the CPU usage spikes to 100%. The browser becomes unresponsive until manually stopped.

Description

Bug Summary:
The UI becomes unresponsive when clicking on the last message (6fee83cf-52c6-4c20-bc44-390858f2e848) in the chat history, causing a CPU spike and browser freeze. (Multi-Model Messaging used)

Reproduction Details

Steps to Reproduce:

  1. Load the attached chat history (file: chat-export-1727554950475.json). (not sure if possible via json, but found no other way)
  2. Attempt to click on the message with ID: 6fee83cf-52c6-4c20-bc44-390858f2e848.
  3. Observe the UI freezing and Chrome’s CPU usage spiking to 100%.

Logs and Screenshots

Browser Console Logs:

Message ID: 6fee83cf-52c6-4c20-bc44-390858f2e848
Stack Trace:
ye (MultiResponseMessages.svelte:191)
c (MultiResponseMessages.svelte:199)

Screenshots/Screen Recordings (if applicable):
[Attach screenshots or screen recordings if available]

Additional Information

  • This issue seems to be linked to the following snippet in the Svelte component: 
    <div
   class="snap-center w-full max-w-full m-1 border {history.messages[messageId]
       ?.modelIdx == modelIdx
       ? `border-gray-100 dark:border-gray-800 border-[1.5px] ${$mobile ? 'min-w-full' : 'min-w-[32rem]'}`
       : `border-gray-50 dark:border-gray-850 border-dashed ${$mobile ? 'min-w-full' : 'min-w-80'}`
   } transition-all p-5 rounded-2xl"
   on:click={() => {
       if (messageId != _messageId) {
           let messageChildrenIds = history.messages[_messageId].childrenIds;
           while (messageChildrenIds.length !== 0) {
               messageId = messageChildrenIds.at(-1);
               messageChildrenIds = history.messages[_messageId].childrenIds;
           }
           history.currentId = _messageId;
           dispatch('change');
       }
   }}
  • The issue could relate to the logic in on:click that handles messageChildrenIds, possibly creating an infinite loop or resource lockup.

Note

Please ensure that the bug report follows the guidelines, including all required details, logs, and reproduction steps. Thank you!

chat-export-1727554950475.json

Originally created by @chrisoutwright on GitHub (Sep 28, 2024). # Bug Report: UI Lockup on Message Interaction ## Installation Method - **Method used:** Manual for Win10 ## Environment - **Open WebUI Version:** v0.3.28 - **Ollama Version:** v0.3.11 - **Operating System:** Windows 10 - **Browser:** Version 129.0.6668.71 (Official Build) (64-bit) , also tried on Edge with same behaviour. **Confirmation:** - [x] I have read and followed all instructions provided in the README.md. - [ ] I am on the latest version of both Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior The chat message should be clickable, allowing interaction without causing the browser to freeze or CPU to spike. ## Actual Behavior When clicking on a specific message (ID: `6fee83cf-52c6-4c20-bc44-390858f2e848`), the UI freezes, and the CPU usage spikes to 100%. The browser becomes unresponsive until manually stopped. ## Description **Bug Summary:** The UI becomes unresponsive when clicking on the last message (`6fee83cf-52c6-4c20-bc44-390858f2e848`) in the chat history, causing a CPU spike and browser freeze. (Multi-Model Messaging used) ## Reproduction Details **Steps to Reproduce:** 1. Load the attached chat history (file: `chat-export-1727554950475.json`). (not sure if possible via json, but found no other way) 2. Attempt to click on the message with ID: `6fee83cf-52c6-4c20-bc44-390858f2e848`. 3. Observe the UI freezing and Chrome’s CPU usage spiking to 100%. ## Logs and Screenshots **Browser Console Logs:** ``` Message ID: 6fee83cf-52c6-4c20-bc44-390858f2e848 Stack Trace: ye (MultiResponseMessages.svelte:191) c (MultiResponseMessages.svelte:199) ``` **Screenshots/Screen Recordings (if applicable):** [Attach screenshots or screen recordings if available] ## Additional Information - This issue seems to be linked to the following snippet in the Svelte component: ```html <div class="snap-center w-full max-w-full m-1 border {history.messages[messageId] ?.modelIdx == modelIdx ? `border-gray-100 dark:border-gray-800 border-[1.5px] ${$mobile ? 'min-w-full' : 'min-w-[32rem]'}` : `border-gray-50 dark:border-gray-850 border-dashed ${$mobile ? 'min-w-full' : 'min-w-80'}` } transition-all p-5 rounded-2xl" on:click={() => { if (messageId != _messageId) { let messageChildrenIds = history.messages[_messageId].childrenIds; while (messageChildrenIds.length !== 0) { messageId = messageChildrenIds.at(-1); messageChildrenIds = history.messages[_messageId].childrenIds; } history.currentId = _messageId; dispatch('change'); } }} ``` - The issue could relate to the logic in `on:click` that handles `messageChildrenIds`, possibly creating an infinite loop or resource lockup. ## Note Please ensure that the bug report follows the guidelines, including all required details, logs, and reproduction steps. Thank you! [chat-export-1727554950475.json](https://github.com/user-attachments/files/17176200/chat-export-1727554950475.json)
GiteaMirror commented 2025-11-11 15:03:06 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Sep 29, 2024):

Good catch, fix on dev! Testing wanted here!

@tjbck commented on GitHub (Sep 29, 2024): Good catch, fix on dev! Testing wanted here!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2233
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?