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

use oceanbase has memory leak #15147

New Issue
Closed
opened 2026-02-21 19:20:25 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:20:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @Sos-Zachary on GitHub (Jul 6, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. select to use oceanbase in .env
  2. start dify server by docker compose
  3. build a rag-server and runing it last for several days
  4. suddenly one day the kb-search will report a "mysql-error"
  5. restart all dify server will fix this problem
  6. check in oceanbase observer.log we can see a alloc fail error

WARN [USING_LOG_PREFIX] print_alloc_failed_msg (alloc_failed_reason.cpp:141) [1606614][TimerWK5_AutoLSLocRpc][T0][YB42AC120005-0006374F5D7C6829-0-0] [lt=36][errcode=-4013] [oops]: alloc failed reason is that server memory has reached the upper limit(server_hold: 6440513536, server_limit: 6442450944, alloc_size: 2097152)

  1. check config in .env，the memory limit is exactly 6G(6442450944)
  2. what problem cause the memory leak?

✔️ Expected Behavior

the oceanbase server is health and safe

❌ Actual Behavior

memory leak

Originally created by @Sos-Zachary on GitHub (Jul 6, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.3.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. select to use oceanbase in .env 2. start dify server by docker compose 3. build a rag-server and runing it last for several days 4. suddenly one day the kb-search will report a "mysql-error" 5. restart all dify server will fix this problem 6. check in oceanbase observer.log we can see a alloc fail error > WARN [USING_LOG_PREFIX] print_alloc_failed_msg (alloc_failed_reason.cpp:141) [1606614][TimerWK5_AutoLSLocRpc][T0][YB42AC120005-0006374F5D7C6829-0-0] [lt=36][errcode=-4013] [oops]: alloc failed reason is that server memory has reached the upper limit(server_hold: 6440513536, server_limit: 6442450944, alloc_size: 2097152) 7. check config in .env，the memory limit is exactly 6G(6442450944) 8. what problem cause the memory leak? ### ✔️ Expected Behavior the oceanbase server is health and safe ### ❌ Actual Behavior memory leak
yindo added the 🐞 bugstaleperformance labels 2026-02-21 19:20:25 -05:00
yindo closed this issue 2026-02-21 19:20:25 -05:00
yindo commented 2026-02-21 19:20:25 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 23, 2025):

Hi, @Sos-Zachary. I'm Dosu (https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a memory leak issue with OceanBase when using Dify version 1.3.0 in a self-hosted Docker setup.
  • After several days, the rag-server hits a "mysql-error" due to OceanBase reaching its 6GB memory limit, causing allocation failures.
  • Restarting the server temporarily resolves the issue.
  • No further updates or troubleshooting information has been provided since your initial report.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here.
  • If I don’t hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 23, 2025): Hi, @Sos-Zachary. I'm Dosu (https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a memory leak issue with OceanBase when using Dify version 1.3.0 in a self-hosted Docker setup. - After several days, the rag-server hits a "mysql-error" due to OceanBase reaching its 6GB memory limit, causing allocation failures. - Restarting the server temporarily resolves the issue. - No further updates or troubleshooting information has been provided since your initial report. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here. - If I don’t hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
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 performance stale 🐞 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#15147
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?