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

error: signal: killed #15442

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

Originally created by @1061862797 on GitHub (Jul 16, 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.6

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

使用文档提取器包含5万行的excel表格，传入代码节点，节点运行后报错。尝试过2万行的excel运行是成功的。错误信息如图：

Image

✔️ Expected Behavior

使用文档提取器包含5万行的excel表格，传入代码节点，节点运行后报错。尝试过2万行的excel运行是成功的。错误信息如图：

Image

❌ Actual Behavior

No response

Originally created by @1061862797 on GitHub (Jul 16, 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.6 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 使用文档提取器包含5万行的excel表格，传入代码节点，节点运行后报错。尝试过2万行的excel运行是成功的。错误信息如图： <img width="1387" height="455" alt="Image" src="https://github.com/user-attachments/assets/5c8bae3e-ce35-4247-b9d2-257318090ad2" /> ### ✔️ Expected Behavior 使用文档提取器包含5万行的excel表格，传入代码节点，节点运行后报错。尝试过2万行的excel运行是成功的。错误信息如图： <img width="1387" height="455" alt="Image" src="https://github.com/user-attachments/assets/5c8bae3e-ce35-4247-b9d2-257318090ad2" /> ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:21:45 -05:00
yindo commented 2026-02-21 19:21:46 -05:00
Author
Owner
Copy Link
Copy Source

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

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

The "error: signal: killed" is almost certainly due to the process running out of memory when handling very large Excel files. Dify's document extractor loads the entire Excel sheet into memory using Pandas and openpyxl, and there are no built-in limits or optimizations for large files—so with 50,000 rows, memory usage can spike and the OS or Docker kills the process, while 20,000 rows stays within your resource limits (source).

To work around this, you can either increase the memory allocated to your Docker container, or split your Excel files into smaller chunks (e.g., under 20,000 rows each) before uploading. There are currently no chunking or batching features for Excel extraction in Dify v1.6, so handling large files efficiently would require code changes or pre-processing (source).

For confirmation and more details, check your Docker/container logs for out-of-memory (OOM) errors. If handling large files is a common need, you might consider proposing or contributing a chunked processing feature, as similar strategies have been used elsewhere in Dify for large batch processing (PR #9989).

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Jul 16, 2025): <!-- Greeting --> Hi @1061862797! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The "error: signal: killed" is almost certainly due to the process running out of memory when handling very large Excel files. Dify's document extractor loads the entire Excel sheet into memory using Pandas and openpyxl, and there are no built-in limits or optimizations for large files—so with 50,000 rows, memory usage can spike and the OS or Docker kills the process, while 20,000 rows stays within your resource limits [(source)](https://github.com/langgenius/dify/blob/a3ced1b5a6b7a9dbf49ea14656654e279d16118c/api/core/rag/extractor/excel_extractor.py). To work around this, you can either increase the memory allocated to your Docker container, or split your Excel files into smaller chunks (e.g., under 20,000 rows each) before uploading. There are currently no chunking or batching features for Excel extraction in Dify v1.6, so handling large files efficiently would require code changes or pre-processing [(source)](https://github.com/langgenius/dify/blob/a3ced1b5a6b7a9dbf49ea14656654e279d16118c/api/core/rag/extractor/excel_extractor.py). For confirmation and more details, check your Docker/container logs for out-of-memory (OOM) errors. If handling large files is a common need, you might consider proposing or contributing a chunked processing feature, as similar strategies have been used elsewhere in Dify for large batch processing [(PR #9989)](https://github.com/langgenius/dify/pull/9989). <!-- 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/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5fc008a1-b39f-428c-bf1e-9f19a6b8dcff?feedback_type=other)</sup>&nbsp;&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/22519)
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
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#15442
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?