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
Does the crash reporter show up with any backtrace?
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?
changing status
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
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!