Bug Report

Description

Memory leak/lock up Downloading Reranker through Settings

Bug Summary:
[Provide a brief but clear summary of the bug]
Tried pulling BAAI/bge-reranker-v2-m3 through the Settings -> Documents > Hybrid Search menu and it memory leaked. Perhaps because bge reranker v2 m3 isn't available in ollama model repo?

Fixed by stopping the container and editing config.json to set enable_hybrid_search to false and reranking_model to null then restarting.

Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Pull BAAI/bge-reranker-v2-m3 through the Settings -> Documents > Hybrid Search menu

Expected Behavior:
[Describe what you expected to happen.]
Download and pull the reranking model.

Actual Behavior:
[Describe what actually happened.]
Memory leaked and locked up

Environment

• Open WebUI Version: [e.g., 0.1.120]

• v0.3.2

• Ollama (if applicable): [e.g., 0.1.30, 0.1.32-rc1]

• 0.1.42

• Operating System: [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04]

• Docker, armbian

• Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]

Reproduction Details

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.

Logs and Screenshots

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

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

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

Installation Method

[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]

Additional Information

[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]

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!