High CPU usage (linux installed via flatpak/snapd)

[cspwizard]

Preflight Checklist

• [ x] I agree to follow the Code of Conduct that this project adheres to.
• [ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
High CPU usage of draw.io app in linux. It consumes more that 50% even nothing is happening. Simply opened the chard and leave it idle in background.

chart isn't small, but still...

To Reproduce
Steps to reproduce the behavior:

1. Create chart with a big number of elements
2. Open it
3. Do nothing
4. See high CPU usage

Expected behavior
CPU should be idle, when nothing is going on in the app

Screenshots
If applicable, add screenshots to help explain your problem.

draw.io version (In the Help->About menu of the draw.io editor):

• draw.io version 25.0.1 (also reproduced on previous versions)

Desktop (please complete the following information):

• OS: Linux (Xubuntu 24.10)

Additional context
Add any other context about the problem here.

[davidjgraph]

Does this still happen with 26.2.15?

[cspwizard]

yep, still ~35-50% cpu usage while idle, also periodically spikes IO

[davidjgraph]

Valid as this might be, it appears to be boundary case and we cannot justify the effort tracking down such a case, apologies.

[cspwizard]

is there any way I can help with debug/looking for root cause?

[draw-io-triage-bot]

👋 Following up on this issue.

---

📝 Still Needed

To help resolve this issue, we still need:

• installation_method: User mentions flatpak/snapd in title but doesn't specify which one was used or if issue occurs with both
• sample_file: A sample diagram file that reproduces the issue would help with debugging
• system_specs: CPU model, RAM, and other system specifications could be relevant for performance issues
• browser_process_breakdown: Since draw.io desktop is Electron-based, a breakdown of which processes are consuming CPU would be helpful
• profiling_data: Performance profiling data or developer tools insights could help identify the root cause

---

---

_{🤖 A maintainer will review this soon. This is an automated followup.}