CherryHQ/cherry-studio

[Discussion]: cherry studio读取excel文件后程序未响应

Open

#15.206 geöffnet am 20. Mai 2026

Auf GitHub ansehen
 (0 Kommentare) (1 Reaktion) (0 zugewiesene Personen)TypeScript (45.688 Stars) (4.338 Forks)batch import
MCPdiscussionhelp wanted

Beschreibung

Issue Checklist

  • I understand that issues are meant for feedback and problem-solving, not for venting, and I will provide as much detail as possible to help resolve the issue.
  • I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
  • I confirm that I am here to ask questions and discuss issues, not to report bugs or request features.

Platform

Windows

Version

1.9.6

Your Question

excel文件不到2M，调用excel-mcp读取文件后，cherry studio刚开始还好好的。突然就卡住（未响应）。等了一阵子又好了

Context

No response

Additional Information

Priority

Medium (Would like a response soon)

Contributor Guide

Tech Stack
typescriptnodejs
Domain
desktopperformance
Issue Type
performance
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
half day
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
fresh
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
needs investigation
Voraussetzungen
basic understanding of Node.js event loopfamiliarity with Excel file parsing
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
30
Research-Richtung
Reproduce the issue by opening an Excel file (~2MB) using the excel mcp feature in Cherry Studio on Windows. The app freezes temporarily, likely due to synchronous file processing blocking the event loop. Investigate the excel mcp integration in the codebase (likely in src/ or packages/ directory) to identify where the file is read and whether it uses synchronous or asynchronous APIs. Consider proposing a fix using streaming or worker threads to keep the UI responsive. Check for existing issues or PRs related to file handling performance.