langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Launching Frontend locally maxes out RAM/CPU usage and crashes. #21871

New Issue
Closed
opened 2026-02-21 20:14:40 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:14:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @adi13v on GitHub (Jan 23, 2026).

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

Can't reach there

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Just followed the guide to getting started on /web

  1. Install all the dependencies
  2. set env.local
  3. try pnpm run dev

✔️ Expected Behavior

The frontend should load! My machine is i7 with 16 gigs of RAM, which is well above the given system requirements, so it's not expected to be a hardware limitation.

❌ Actual Behavior

maxed out memory and CPU usage, and then crashed my browser.

Originally created by @adi13v on GitHub (Jan 23, 2026). ### 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 Can't reach there ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce ### Just followed the guide to getting started on `/web` 1. Install all the dependencies 2. set env.local 3. try `pnpm run dev` ### ✔️ Expected Behavior The frontend should load! My machine is i7 with 16 gigs of RAM, which is well above the given system requirements, so it's not expected to be a hardware limitation. ### ❌ Actual Behavior maxed out memory and CPU usage, and then crashed my browser.
yindo added the 🐞 bug label 2026-02-21 20:14:40 -05:00
yindo closed this issue 2026-02-21 20:14:40 -05:00
yindo commented 2026-02-21 20:14:40 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 23, 2026):

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

This is a known issue with Dify's frontend development setup: the main cause of high RAM/CPU usage and crashes is the codeInspectorPlugin, which is enabled by default in development and significantly slows down Next.js builds. Disabling this plugin in web/next.config.js will greatly improve performance. Also, make sure the bundle analyzer is not enabled (leave the ANALYZE env variable unset during dev), and confirm ESLint is fully disabled in dev mode. Setting NEXT_TELEMETRY_DISABLED=1 in your .env.local can also help reduce overhead. For even faster builds, consider upgrading to Next.js 15.5 and enabling TurboPack in development. If you only need the backend, you can use a prebuilt frontend Docker image to avoid running the local dev server. More details and step-by-step instructions are available in this discussion and this issue.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 23, 2026): <!-- Greeting --> Hi @adi13v! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known issue with Dify's frontend development setup: the main cause of high RAM/CPU usage and crashes is the codeInspectorPlugin, which is enabled by default in development and significantly slows down Next.js builds. Disabling this plugin in `web/next.config.js` will greatly improve performance. Also, make sure the bundle analyzer is not enabled (leave the `ANALYZE` env variable unset during dev), and confirm ESLint is fully disabled in dev mode. Setting `NEXT_TELEMETRY_DISABLED=1` in your `.env.local` can also help reduce overhead. For even faster builds, consider upgrading to Next.js 15.5 and enabling TurboPack in development. If you only need the backend, you can use a prebuilt frontend Docker image to avoid running the local dev server. More details and step-by-step instructions are available in [this discussion](https://github.com/langgenius/dify/discussions/24603) and [this issue](https://github.com/langgenius/dify/issues/23938). <!-- 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/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/062fa405-0396-4205-8308-b5903b8e1a9c?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20with%20Dify%27s%20frontend%20development%20setup%3A%20the%20main%20cause%20of%20high%20RAM/CPU%20usage%20and%20crashes%20is%20the%20codeInspectorPlugin%2C%20which%20is%20enabled%20by%20default%20in%20development%20and%20significantly%20slows%20down%20Next.js%20builds.%20Disabling%20this%20plugin%20in%20%60web/next.config.js%60%20will%20greatly%20improve%20performance.%20Also%2C%20make%20sure%20the%20bundle%20analyzer%20is%20not%20enabled%20%28leave%20the%20%60ANALYZE%60%20env%20variable%20unset%20during%20dev%29%2C%20and%20confirm%20ESLint%20is%20fully%20disabled%20in%20dev%20mode.%20Setting%20%60NEXT_TELEMETRY_DISABLED%3D1%60%20in%20your%20%60.env.local%60%20can%20also%20help%20reduce%20overhead.%20For%20even%20faster%20builds%2C%20consider%20upgrading%20to%20Next.js%2015.5%20and%20enabling%20TurboPack%20in%20development.%20If%20you%20only%20need%20the%20backend%2C%20you%20can%20use%20a%20prebuilt%20frontend%20Docker%20image%20to%20avoid%20running%20the%20local%20dev%20server.%20More%20details%20and%20step-by-step%20instructions%20are%20available%20in%20%5Bthis%20discussion%5D%28https%3A//github.com/langgenius/dify/discussions/24603%29%20and%20%5Bthis%20issue%5D%28https%3A//github.com/langgenius/dify/issues/23938%29.)&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/31477)
yindo commented 2026-02-21 20:14:40 -05:00
Author
Owner
Copy Link
Copy Source

@hyoban commented on GitHub (Jan 24, 2026):

I am unable to reproduce it, but I believe this is indeed a possibility. Unfortunately, there is nothing we can do about it at this time.

@hyoban commented on GitHub (Jan 24, 2026): I am unable to reproduce it, but I believe this is indeed a possibility. Unfortunately, there is nothing we can do about it at this time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21871
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?