mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-24 20:14:58 -05:00
Crash when uploading an image with model Llama 3 70B #1007
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#1007
Reference in New Issue
Block a user
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?
Originally created by @Hugobox on GitHub (May 22, 2024).
Bug Report
Description
Bug Summary:
We use model Llama 3 70B via litellm and it works well, but as soon as we upload any image file (png or jpg) the webui becomes unresponsive and has to be restarted, no error found in logs. PDFs do not crash webui, only images.
Normally with models that do not support image uploads like GPT3.5-turbo, we get the following error message:
"Uh-oh! There was an issue connecting to gpt-3.5-turbo.
External: Invalid content type. image_url is only supported by certain models."
But it seems like with Llama 3 70B via litellm this file type check is not done correctly.
Steps to Reproduce:
use model Llama 3 70B via litellm
open webui, set model to Llama 3 70B
test model with text prompt, notice it works
test model with image upload and text prompt, notice it becomes unresponsive.
Expected Behavior:
[Describe what you expected to happen.]
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: v0.1.125
Operating System: [Ubuntu 20.04]
Reproduction Details
Confirmation:
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
Docker-compose file
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!