Bug 472455 - Memory leak after opening large file with lsp plugin enabled
Summary: Memory leak after opening large file with lsp plugin enabled
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: application (other bugs)
Version First Reported In: 22.12.3
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-21 06:22 UTC by calvinchaochao
Modified: 2023-07-21 07:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description calvinchaochao 2023-07-21 06:22:02 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Enable lsp plugin and install dart analyzer serber
2. Randomly open a large dart source file(eg. one from flutter sdk)
3. Memory will leak and the UI will become slow

OBSERVED RESULT
Memory leak and slow ui

EXPECTED RESULT
no memory leak

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Waqar Ahmed 2023-07-21 07:15:24 UTC
Hi, you need to update your Kate version and try again. I have put in a few fixes for this issue in the latest release and the one before that.

To try the latest, you'll have to build it yourself which is pretty easy to do on debian unstable. Pasting the instructions below:
- Install build dependencies of kate and build essential tools (gcc, cmake) from distro packages
- Clone kate git repo: https://invent.kde.org/utilities/kate/
- cd kate
- mkdir build && cd build
- cmake .. && make -j4

Once the above finishes successfully the kate binary can be found in the 'bin' subdirectory. Run `./bin/kate`

If the latest one is also slow, please reopen the issue.