| Summary: | kate stops responding with big file | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Germano Massullo <germano.massullo> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde.podagric, kde |
| Priority: | NOR | ||
| Version: | 20.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/frameworks/ktexteditor/-/commit/98424e067240fc6243434631ae2f95f5e9aca49e | Version Fixed In: | |
| Attachments: |
kate valgrind
affected file |
||
Created attachment 137834 [details]
affected file
Thanks for the report. I believe the observed slowdown was fixed in the latest ktexteditor. this has really improved navigation, but there are still slowness issues when copying large selections. Example: when selecting 40 thousand lines and copying or cutting them to another tab Nice. I guess there will be similar issue. IMHO there is no reason why copy should not be fast. The cutting case might be more difficult. |
Created attachment 137833 [details] kate valgrind 1) Open the TXT inside the attached file. 2) press CTRL + END in order to reach the end of the file 3) press CTRl + F and search for tmp 4) Kate will stop responding and increasing RAM usage till you kill the process I collected output from $ valgrind --leak-check=full \ --show-leak-kinds=all \ --track-origins=yes \ --verbose \ --log-file=kate-valgrind-out.txt \ kate