Bug 502195

Summary:	Crash whenever a long-sized file is loaded and the find command is triggered
Product:	[Applications] kate	Reporter:	MV <meetvekaria>
Component:	kwrite	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	christoph, john.kizer, waqar.17a
Priority:	NOR
Version First Reported In:	24.12.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Screenshot showing file statistics

Description MV 2025-03-30 07:09:59 UTC

Created attachment 179860 [details]
Screenshot showing file statistics

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
Whenever we open a file having long line of codes, (in my case, it crashed for a theme css file I opened for Obsidian having statistics as per attached screenshot), and when I either try to scroll quickly or search a term using FIND function, the app hangs and crashes.

This does not happen with other text editors on the same OS, same computer. Therefore, it is not an issue of RAM or STORAGE or OS.

STEPS TO REPRODUCE
1. Open a large file.
2. Scroll quickly or search for a term.

OBSERVED RESULT
Application crashes.

EXPECTED RESULT
Find function should work.

SCREENSHOT

Comment 1 Christoph Cullmann 2025-03-30 14:25:57 UTC

Does the crash reporter show up with any backtrace?

Comment 2 Waqar Ahmed 2025-03-30 17:14:17 UTC

Was not able to reproduce with minified jquery sources. Is it possible for you to share the file? Also which find are you using, the plugin or just ctrl+f?

Comment 3 Waqar Ahmed 2025-04-03 09:58:55 UTC

changing status

Comment 4 MV 2025-04-03 15:46:29 UTC

I was using the normal find CTRL + F. And no, there is no crash reporter or any message or alert that shows up. The application simply stops responding. And then I have to hard close it through task manager or it sometimes even closes on its own without any alert or report.

For reference, you can use following file. This has a very long length in the file.

https://github.com/chrisgrieser/shimmering-focus/blob/main/theme.css

Comment 5 John Kizer 2025-04-11 03:45:33 UTC

Hi - if the Crashed Processes Viewer doesn't appear with a prompt to submit a full crash report, backtraces can be generated through other methods as well: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports 

Could you please provide a backtrace using whichever method is viable on your device? Thanks!

Comment 6 Bug Janitor Service 2025-04-26 03:47:23 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Bug Janitor Service 2025-05-11 03:46:52 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.