v1.7.1 Flickering issue in Chrome #15787

Open
opened 2026-02-21 19:23:19 -05:00 by yindo · 4 comments
Owner

Originally created by @ihoskovecpetr on GitHub (Jul 30, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Seem that any larger Chatflow app does start flickering. This was not an issue in previous version (1.6.1), but its now present in 1.7.1

This issue is only in Chrome, tested in Safari and it seem to be displaying correctly.
There is and issue with rendering/flickering before and after I run preview.
Flickering is not precent in Chrome when I use the Incognito mode (so could be an extension issue?)

✔️ Expected Behavior

Not flicker.

Actual Behavior

App elements are flickering, sometimes not displaying, then randomly disappearing etc.

videos:

video

screenshots:

Image Image
Originally created by @ihoskovecpetr on GitHub (Jul 30, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Seem that any larger Chatflow app does start flickering. This was not an issue in previous version (1.6.1), but its now present in 1.7.1 This issue is only in Chrome, tested in Safari and it seem to be displaying correctly. There is and issue with rendering/flickering before and after I run preview. **Flickering is not precent in Chrome when I use the Incognito mode (so could be an extension issue?)** ### ✔️ Expected Behavior Not flicker. ### ❌ Actual Behavior App elements are flickering, sometimes not displaying, then randomly disappearing etc. videos: [video](https://github.com/user-attachments/assets/9f0db883-3a19-44ae-8909-3e2562406332) screenshots: <img width="1705" height="1149" alt="Image" src="https://github.com/user-attachments/assets/4873458c-3b6f-400b-a69a-a45555d1700e" /> <img width="582" height="737" alt="Image" src="https://github.com/user-attachments/assets/1ed6aa58-e2d8-4e57-8dfe-0ffe208c77ba" />
yindo added the 🐞 buggood first issue labels 2026-02-21 19:23:19 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jul 30, 2025):

Hi @ihoskovecpetr! I'm Dosu and I’m helping the dify team.

There are no existing tickets or documentation directly addressing this Chrome flickering issue in Dify v1.7.1, but based on the code and recent changes, the most likely causes are frontend rendering and state management updates. In particular, CSS transitions on workflow panels and nodes, frequent state updates via Zustand (especially with ResizeObserver and layout changes), and forced rerenders in the workflow UI can trigger excessive DOM updates, which Chrome handles less gracefully than Safari.

You can try these workarounds:

  • Temporarily disable or reduce CSS transitions for .workflow-panel-animation .react-flow__viewport and .workflow-node-animation .react-flow__node in your custom CSS to see if that reduces flickering.
  • Throttle or debounce ResizeObserver updates in the workflow component to avoid rapid state changes.
  • Check if toggling the nodeAnimation state or reducing forced rerenders (like setControlPromptEditorRerenderKey(Date.now())) helps.
  • Make sure all dependencies (especially mermaid) are properly transpiled for Chrome compatibility, as modern JS syntax in dependencies can cause rendering issues if not handled by your build process [source].

If the issue persists, capturing a Chrome DevTools performance profile during the flicker can help pinpoint which updates or styles are causing the problem.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 30, 2025): <!-- Greeting --> Hi @ihoskovecpetr! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> There are no existing tickets or documentation directly addressing this Chrome flickering issue in Dify v1.7.1, but based on the code and recent changes, the most likely causes are frontend rendering and state management updates. In particular, CSS transitions on workflow panels and nodes, frequent state updates via Zustand (especially with ResizeObserver and layout changes), and forced rerenders in the workflow UI can trigger excessive DOM updates, which Chrome handles less gracefully than Safari. You can try these workarounds: - Temporarily disable or reduce CSS transitions for `.workflow-panel-animation .react-flow__viewport` and `.workflow-node-animation .react-flow__node` in your custom CSS to see if that reduces flickering. - Throttle or debounce ResizeObserver updates in the workflow component to avoid rapid state changes. - Check if toggling the `nodeAnimation` state or reducing forced rerenders (like `setControlPromptEditorRerenderKey(Date.now())`) helps. - Make sure all dependencies (especially `mermaid`) are properly transpiled for Chrome compatibility, as modern JS syntax in dependencies can cause rendering issues if not handled by your build process [[source]](https://github.com/langgenius/dify/issues/19798). If the issue persists, capturing a Chrome DevTools performance profile during the flicker can help pinpoint which updates or styles are causing the problem. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f9be77dc-893f-497c-bde6-972e08c0e029?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23200)
Author
Owner

@oOhyeahh commented on GitHub (Jul 30, 2025):

It happens to me as well when I use dark theme.

@oOhyeahh commented on GitHub (Jul 30, 2025): It happens to me as well when I use dark theme.
Author
Owner

@ihoskovecpetr commented on GitHub (Jul 31, 2025):

It seem to be fixed, have been using Dify today, same version, same browser and laptop, no rendering issue anymore.

@ihoskovecpetr commented on GitHub (Jul 31, 2025): It seem to be fixed, have been using Dify today, same version, same browser and laptop, no rendering issue anymore.
Author
Owner

@AnotiaWang commented on GitHub (Sep 29, 2025):

This issue still persists on Dify v1.9.1, making it completely unusable.

Browser: Vivaldi 7.6.3797.56 (Stable channel) (arm64)
System: macOS Tahoe 26.0 (issue also exists on macOS 15)

@crazywoola

https://github.com/user-attachments/assets/d7cefd7f-3661-4016-a9cd-387e5003349c

@AnotiaWang commented on GitHub (Sep 29, 2025): This issue still persists on Dify v1.9.1, making it completely unusable. Browser: Vivaldi 7.6.3797.56 (Stable channel) (arm64) System: macOS Tahoe 26.0 (issue also exists on macOS 15) @crazywoola https://github.com/user-attachments/assets/d7cefd7f-3661-4016-a9cd-387e5003349c
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15787