-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug][iOS/Swift SDK] Multiple image input to vision models will throw error from TVM #3044
Labels
bug
Confirmed bugs
Comments
Neet-Nestor
changed the title
[Bug] Sending images with large dimensions into vision models will break TVM
[Bug] Image input to vision models will throw error from TVM
Nov 22, 2024
Neet-Nestor
changed the title
[Bug] Image input to vision models will throw error from TVM
[Bug][iOS/Swift SDK] Image input to vision models will throw error from TVM
Nov 22, 2024
Neet-Nestor
changed the title
[Bug][iOS/Swift SDK] Image input to vision models will throw error from TVM
[Bug][iOS/Swift SDK] Multiple image input to vision models will throw error from TVM
Nov 22, 2024
I have the same issue on Ubuntu 24.04. Using openai API with mlc_llm serve of phi-3.5-vision. Compiled from source |
|
And it only goes wrong if the second image is larger than the first image. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bug
When using the
mlc-llm
Swift package to chat with vision language models, specifically thePhi-3-vision-instruct
model, errors occur when attempting to input an image for the second time or input multiple images simutaneously. The first image input processes correctly, but subsequent attempts result in one of the following errors:To Reproduce
Steps to reproduce the behavior:
MLCEngine.chatCompletion()
as base64 encoded url. This image shall input into the pipeline and decode tokens correctly.or,
MLCEngine.chatCompletion()
as base64 encoded url.Expected behavior
The model should process multiple image inputs without throwing exceptions.
Environment
The text was updated successfully, but these errors were encountered: