mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
Significant Latency Increase & Errors with Images in Gemini Plugin v0.0.6+ #169
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 @Hzao on GitHub (Apr 3, 2025).
Self Checks
Dify version
1.1.3
Plugin version
0.0.6 and plus
Cloud or Self Hosted
Cloud
Steps to reproduce
Description:
Since updating the Dify Gemini plugin (https://marketplace.dify.ai/plugins/langgenius/gemini) to version 0.0.6 or later, I've encountered two critical issues with the vision model:
These 2 issues seem related: The latency issue appears to be related to image size, as smaller images (1MB) exhibit shorter processing times, but still longer than previous versions.
Steps to Reproduce:
Issue Environment
Dify with Gemini plugin version 0.0.6 or later.
Model
Google Gemini 2.0 Flash 001
Input
Calling the model with an image (You can find the image I'm using in the attachment).
Task
Perform a task that utilizes the vision capabilities of the model (e.g., image analysis, description).
You can try with my exported DSL and all my testing images in attachment.zip too.
attachments.zip
Comparison (Testing with IMG_Normal.png, with the size of 3.1 MB)
Issue with file size
I noticed that, this issue might be related to file size:
-If we try with a 2.6MB image: 41 seconds. (❌Too Slow)
2-6MB image inputs are common use cases, and 1 minute of processing time is excessively long. So I hope this information is helpful in resolving the issue.
✔️ Error log
No response
@hjlarry commented on GitHub (Apr 3, 2025):
I can't reproduce it on
cloud.dify.ai, use your dsl, not change anythingimage normal
image large
@Hzao commented on GitHub (Apr 3, 2025):
All my previous tests were also operated on cloud.dify.ai, on both plugin version v0.0.6 & v0.1.1.
Can you confirm your plugin version?
@hjlarry commented on GitHub (Apr 3, 2025):
My plugin version is v0.1.2, but versions
0.1.2and0.1.1are almost identical.@Hzao commented on GitHub (Apr 3, 2025):
I tried it out, and still, I can reproduce the issue on v0.1.2 and when switched back to v0.0.5, it's back to normal.
This is a demo video that I recorded, in which I use v0.1.2 first but failed, then switched to v0.0.5 and succeeded.
https://github.com/user-attachments/assets/e4a3546f-5e17-4de1-af38-a52c1beed979
(Although it's recorded using Safari, I can reproduce it in Chrome based browser too.)
I recommend you switch gemini plugin version back and forth, and refresh the browser to make sure it takes effect.
@hjlarry commented on GitHub (Apr 5, 2025):
I have encountered this issue both in the cloud environment and my local setup, and it’s quite strange.
As you can see, the update only added a model configuration. I also reviewed the plugin-daemon changes between Feb 27 and Mar 2, but there doesn’t seem to be anything related to this issue.
@Yeuoly Could you assist in debugging this problem?
@linqinguang commented on GitHub (Apr 9, 2025):
I also encountered the same problem. I used 4 model providers, and after troubleshooting, I obtained the following information which may be helpful:
The 4 providers are shown in the figure.

The version of each plugin is as follows:
@kurokobo commented on GitHub (Apr 10, 2025):
https://github.com/langgenius/dify/issues/17799#issuecomment-2794481200
@moshilangzi commented on GitHub (May 15, 2025):
In dify v1.4.0,the error occurs again:
use tongyi plugin: qwen2.5-vl-72b-instruct,upload 5 images ,then chat with model:
Run failed: [tongyi] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"encountered an error: invalid character '\u003c' looking for beginning of value status: 502 Bad Gateway original response: \u003chtml\u003e"}
other plugins are the same error!
@QuantumGhost commented on GitHub (May 15, 2025):
Hi @moshilangzi,
Thank you for your feedback! We're actively looking into this issue.
I also noticed that you've reported a similar issue in the Dify repository. To keep the discussion centralized and avoid duplication, I recommend continuing the conversation over there.