Misc. bug: New web UI is lame with number of existing conversations

[gnusupport]

Name and Version

llama-cli --version
ggml_cuda_init: GGML_CUDA_FORCE_MMQ: no
ggml_cuda_init: GGML_CUDA_FORCE_CUBLAS: no
ggml_cuda_init: found 1 CUDA devices:
Device 0: NVIDIA GeForce RTX 3090, compute capability 8.6, VMM: yes
version: 2279 (de41f2b)
built with cc (Debian 14.2.0-19) 14.2.0 for x86_64-linux-gnu

Operating systems

Linux

Which llama.cpp modules do you know to be affected?

llama-server

Command line

/usr/local/bin/llama-server --jinja -fa on -c 32768 -ngl 999 -v --log-timestamps --host 192.168.1.68 -m /mnt/nvme0n1/LLM/quantized/openai_gpt-oss-20b-Q8_0.gguf

Problem description & steps to reproduce

The new web UI is quite different than old, and lacks responsiveness. If I open it with new instance of the browser, or in the anonymous window, it looks fine and good.

However, my old storage has many conversations, not too many, but many.

And in that case the new web UI is totally unresponsive. I can see the chat area, and the upper left and right icons, but:

• left icon (to show or hide conversations) is not working (I guess it needs time to start working, but did not count how long time)
• right icon (settings), also doesn't work
• when starting to write anything in the chat area, I get empty result, ending with totally empty conversation

The way to revive it is that I start clicking on existing conversations, provided they open finally. Then maybe I say "hello" and maybe it starts working.

The new web UI is very uncertain, and has lack of functionality.

First Bad Commit

No response

Relevant log output

[ggerganov]

@allozaur I think this is the same as #14839 (comment)

I experience the same symptoms. The only way to workaround this was to start using the server on a fresh new port that does not have my old conversations.

[allozaur]

@ggerganov @gnusupport

I will take a closer look at this issue this week. I wasn't able to reproduce this last time i checked this issue @ggerganov, but i will do my best to address this and solve this prolbem.

[sultanqasim]

I've been having the same issues. While opening the web UI in private browsing (with no previous conversations), prompts entered in the initial "How can I help you today?" get answered. However, when opening it in my regular browser tab (with extensive past conversation history), entering and submitting a prompt in that initial "How can I help you today?" results causes a blank screen with no response. I need to submit the prompt a second time to get an answer.

These are the errors I saw in my web browser console when not using private browsing:

Uncaught (in promise) Error: https://svelte.dev/e/effect_update_depth_exceeded
    nA http://127.0.0.1:8080/:36
    LA http://127.0.0.1:8080/:36
    flush_effects http://127.0.0.1:8080/:36
    og http://127.0.0.1:8080/:36
    M_ http://127.0.0.1:8080/:37
    <anonymous> http://127.0.0.1:8080/:37
    d4 http://127.0.0.1:8080/:37
    Ju http://127.0.0.1:8080/:37
127.0.0.1:8080:36:2250
Uncaught (in promise) Error: https://svelte.dev/e/effect_update_depth_exceeded
    nA http://127.0.0.1:8080/:36
    LA http://127.0.0.1:8080/:36
    flush_effects http://127.0.0.1:8080/:36
    og http://127.0.0.1:8080/:36
    M_ http://127.0.0.1:8080/:37
    <anonymous> http://127.0.0.1:8080/:37
    d4 http://127.0.0.1:8080/:37
    Ju http://127.0.0.1:8080/:37
    Gg http://127.0.0.1:8080/:37
    Gs http://127.0.0.1:8080/:37
    createConversation http://127.0.0.1:8080/:870
    sendMessage http://127.0.0.1:8080/:870
    K http://127.0.0.1:8080/:876
    I http://127.0.0.1:8080/:861
    app http://127.0.0.1:8080/:36
    Xd http://127.0.0.1:8080/:36
    i http://127.0.0.1:8080/:36
127.0.0.1:8080:36:2250

[allozaur]

@gnusupport @sultanqasim @ggerganov I've found the root cause of this bug and pushed a fix in #16369. Please let me know if this solves the problem on your end as well!

[ggerganov]

It's much better now - writing in the chat always starts generating a new conversation.

However, there is still a problem with the side panel not being rendered properly:

In this situation, clicking on the panel icon in the upper left does nothing.

If I make the window of the browser smaller, it works:

By default I use a 2560x1440 resolution, so if you cannot reproduce, try to increase the resolution and then maximize the window.

[allozaur]

By default I use a 2560x1440 resolution, so if you cannot reproduce, try to increase the resolution and then maximize the window.

I just tested on 3148x1664 resolution on Firefox and Chrome and didn't have this problem, I am not sure why this would happen on one resolution and not on another.

On the other hand I additionally tested with over a thousand conversations and discovered that the issue was still present due to <ActionDropdown> also being rendered for each item in sidebar, so i've updated it to render conditionally only for the conversation item that user is currently hovering (7656f61). Please check out #16369 and let me know!

[ggerganov]

Almost working - for some reason the panel expands all input prompts instead of showing the short version:

webui.mp4

[allozaur]

@ggerganov fixed this with 8f46a4c

[ggerganov]

Hallelujah! Everything works now