Bug 509879 - Kate hangs when opening file
Summary: Kate hangs when opening file
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.12.3
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-24 17:58 UTC by Linus Götzfried
Modified: 2025-09-24 19:31 UTC (History)
2 users (show)

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


Attachments
The file which causes the error. (8.33 KB, text/x-c++hdr)
2025-09-24 17:58 UTC, Linus Götzfried
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Linus Götzfried 2025-09-24 17:58:39 UTC
Created attachment 185220 [details]
The file which causes the error.

SUMMARY
When I open a certain file in Kate, after less than a minute my computer hangs. I cannot do anything but power it off (REISUB works).

STEPS TO REPRODUCE
1. Open the attached file.
2. Try to do anything with Kate (editing the file, going to Settings, ...). I am not sure whether this is necessary.

OBSERVED RESULT
The computer becomes unresponsive and the screen freezes. I can merely power it off.

EXPECTED RESULT
Normal behaviour.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: I use GNOME and Kate merely as application. My OS is Debian 12.
KDE Plasma Version: 5.103.0-1+deb12u1
KDE Frameworks Version: 5.103.0-1+deb12u1
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I have the LSP client enabled (the file is C++ source code). 
Unfortunately, since my computer freezes entirely, I have been unable to create a backtrace. I would be grateful if you could explain to me how to do it in such a case.
Comment 1 Christoph Cullmann 2025-09-24 18:21:58 UTC
Works for me with 25.08.
Comment 2 Linus Götzfried 2025-09-24 18:34:47 UTC
Well - after having edited the file (removing some undeclared variables), it also works for me. It may have been the Clang daemon crashing my computer since it had to produce too many errors. Anyway, thanks.
Comment 3 Christoph Cullmann 2025-09-24 18:40:47 UTC
(In reply to Linus Götzfried from comment #2)
> Well - after having edited the file (removing some undeclared variables), it
> also works for me. It may have been the Clang daemon crashing my computer
> since it had to produce too many errors. Anyway, thanks.

That could be, clangd did use some cpu time here, too.
Comment 4 Waqar Ahmed 2025-09-24 19:31:39 UTC
I would suggest that you report this to clangd guys, they might be able to improve the situation. github.com/clangd/clangd/issues/